[lkml]   [2012]   [Jul]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: linux-next : cpuidle - could you add my tree please
    On 07/03/2012 10:59 AM, Rafael J. Wysocki wrote:
    > On Tuesday, July 03, 2012, Daniel Lezcano wrote:
    >> On 07/02/2012 09:49 PM, Rafael J. Wysocki wrote:
    >>> On Monday, July 02, 2012, Daniel Lezcano wrote:
    >>>> On 07/02/2012 11:09 AM, Linus Walleij wrote:
    >>>>> On Mon, Jun 25, 2012 at 3:27 PM, Daniel Lezcano
    >>>>> <> wrote:
    >>>>>> we discussed last week to put in place a tree grouping the cpuidle
    >>>>>> modifications [1]. Is it possible to add the tree ?
    >>>>>> git:// #cpuidle-next
    >>>>> Thanks for doing this.
    >>>>> Since MAINTAINERS is lacking a listed maintainer for cpuidle,
    >>>>> are you also going to add yourself as maintainer and list this
    >>>>> tree in that file, or is this a one-time exercise?
    >>>> I will be glad to do that if Len and Rafael agree on that.
    >>> Len Brown has been a cpuidle maintainer for some time now. Moreover,
    >>> he's been taking patches, but Linus refused to pull his entire tree during the
    >>> last merge window (as you probably know). I honestly don't think this is
    >>> a good enough reason for replacing him as a cpuidle maintainer by force.
    >>> So, you should ask Len whether or not he's willing to pass the cpuidle
    >>> maintenance to someone else.
    >> No, no. You are misunderstanding what I am proposing. I don't want to
    >> replace Len I just want to act as a "proxy". I understand a maintainer
    >> can be busy and could not have enough time to take care of the subsystem
    >> is maintaining during a period because he's too busy for that.
    >> Trust me, I fully understand that :)
    >> As there are a lot of modifications of cpuidle, I am proposing to take
    >> the patches when they are acked-by, to create a consolidated tree,
    >> providing a better integration for cpuidle, a wider testing, preventing
    >> conflicts and facilitating Len's work if he agrees to pull from this tree.
    >> If that makes sense to add myself to the MAINTAINER file as a
    >> co-maintainer (understand: send to me also the patches, so I can take
    >> care of them if Len does not respond), I am ok with that.
    >> It is just about helping :)
    > Cool. :-)
    > So do you have a branch in the cpuidle-next.git tree that isn't going to
    > be rebased?

    No. I am following Linus tree and adding the patches on top of it.

    >>> I know that Len hasn't been responsive recently, but I also know that he
    >>> _does_ respond to inquiries sent directly to him.
    >> Do you mean to its intel address ?
    > Yes, CCing the Len's Intel address won't hurt I think.

    Ok, I will ping him and give him the pointers to the discussion we had.

    -- Daniel

    <> │ Open source software for ARM SoCs

    Follow Linaro: <> Facebook |
    <!/linaroorg> Twitter |
    <> Blog

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2012-07-03 15:21    [W:0.029 / U:45.848 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site