From: Sudeep.KarkadaNagesha@arm.com (Sudeep KarkadaNagesha)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] DT/core: cpu_ofnode updates for v3.12
Date: Thu, 08 Aug 2013 16:49:41 +0100 [thread overview]
Message-ID: <5203BE15.2040506@arm.com> (raw)
In-Reply-To: <CAL_JsqKwHtW4qBkXq=FmOmCrN35Oe+HuDbG=u9BwK8Aas2Paww@mail.gmail.com>
On 08/08/13 16:27, Rob Herring wrote:
> On Thu, Aug 8, 2013 at 9:43 AM, Sudeep KarkadaNagesha
> <Sudeep.KarkadaNagesha@arm.com> wrote:
>> Hi Rob,
>>
>> On 06/08/13 17:11, Sudeep KarkadaNagesha wrote:
>>> Hi Rob,
>>>
>>> The following changes since commit c095ba7224d8edc71dcef0d655911399a8bd4a3f:
>>>
>>> Linux 3.11-rc4 (2013-08-04 13:46:46 -0700)
>>>
>>> are available in the git repository at:
>>>
>>> git://linux-arm.org/linux-skn.git cpu_ofnode_dt
>>>
>>> for you to fetch changes up to d7b5133478afd9e66a338d3125bc37b9a250ef66:
>>>
>>> of/device: add helper to get cpu device node from logical cpu index
>>> (2013-08-06 16:37:15 +0100)
>>>
>>
>> I was not sure whom to send pull request(you or Grant).
>> This needs to be pulled in and present in linux-next before I can send
>> the updates in SoC and cpufreq which depends on this.
>
> With necessary acks, you don't need send these to 3 maintainers. I
> would suggest you send the whole series to cpufreq maintainers to
> merge rather than have them try to manage 2 dependent branches.
>
> Also, something landing in linux-next has no bearing on the process.
> If you do have dependent branches in another tree, then you need to
> insure with that maintainer that the branch is stable and inform the
> 2nd maintainer of the dependency on the branch.
>
Thanks Rob for clarifying.
Hi Rafael,
The complete series[1] was reviewed and acknowledged by appropriate
maintainers.
Since most of the changes are CPUFreq clean-ups, would you take the
complete series through your tree ?
On which branch(bleeding-edge or linux-next) on [2] do I need to base my
pull request ?
Regards,
Sudeep
[1]
http://archive.arm.linux.org.uk/lurker/message/20130722.113211.b5e3bc2a.fr.html
[2] git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
next prev parent reply other threads:[~2013-08-08 15:49 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 16:11 [GIT PULL] DT/core: cpu_ofnode updates for v3.12 Sudeep KarkadaNagesha
2013-08-08 14:43 ` Sudeep KarkadaNagesha
2013-08-08 15:27 ` Rob Herring
2013-08-08 15:49 ` Sudeep KarkadaNagesha [this message]
2013-08-12 8:54 ` Sudeep KarkadaNagesha
2013-08-12 9:03 ` Viresh Kumar
2013-08-12 11:51 ` Rafael J. Wysocki
2013-08-12 12:41 ` Sudeep KarkadaNagesha
2013-08-12 13:13 ` Rafael J. Wysocki
2013-08-12 13:06 ` Sudeep KarkadaNagesha
-- strict thread matches above, loose matches on Subject: below --
2013-08-12 13:27 Sudeep KarkadaNagesha
2013-08-12 13:27 ` Sudeep KarkadaNagesha
2013-08-13 13:00 ` Rafael J. Wysocki
2013-08-13 13:00 ` Rafael J. Wysocki
2013-08-13 15:40 ` Sudeep KarkadaNagesha
2013-08-13 15:40 ` Sudeep KarkadaNagesha
2013-08-13 15:40 ` Sudeep KarkadaNagesha
2013-08-13 18:29 ` Sudeep KarkadaNagesha
2013-08-13 18:29 ` Sudeep KarkadaNagesha
2013-08-13 18:29 ` Sudeep KarkadaNagesha
2013-08-13 21:07 ` Benjamin Herrenschmidt
2013-08-13 21:07 ` Benjamin Herrenschmidt
2013-08-13 21:07 ` Benjamin Herrenschmidt
2013-08-14 10:01 ` Sudeep KarkadaNagesha
2013-08-14 10:01 ` Sudeep KarkadaNagesha
2013-08-14 10:01 ` Sudeep KarkadaNagesha
2013-08-14 11:37 ` Benjamin Herrenschmidt
2013-08-14 11:37 ` Benjamin Herrenschmidt
2013-08-14 11:37 ` Benjamin Herrenschmidt
2013-08-14 13:21 ` Sudeep KarkadaNagesha
2013-08-14 13:21 ` Sudeep KarkadaNagesha
2013-08-14 13:21 ` Sudeep KarkadaNagesha
2013-08-14 22:57 ` Benjamin Herrenschmidt
2013-08-14 22:57 ` Benjamin Herrenschmidt
2013-08-14 22:57 ` Benjamin Herrenschmidt
2013-08-14 12:53 ` Rob Herring
2013-08-14 12:53 ` Rob Herring
2013-08-14 12:53 ` Rob Herring
2013-08-14 13:27 ` Sudeep KarkadaNagesha
2013-08-14 13:27 ` Sudeep KarkadaNagesha
2013-08-14 13:27 ` Sudeep KarkadaNagesha
2013-08-13 18:37 ` Michal Simek
2013-08-13 18:37 ` Michal Simek
2013-08-13 18:37 ` Michal Simek
2013-08-14 8:41 ` Sudeep KarkadaNagesha
2013-08-14 8:41 ` Sudeep KarkadaNagesha
2013-08-14 8:41 ` Sudeep KarkadaNagesha
2013-08-13 18:44 ` Rob Herring
2013-08-13 18:44 ` Rob Herring
2013-08-13 18:44 ` Rob Herring
2013-08-13 19:45 ` Rafael J. Wysocki
2013-08-13 19:45 ` Rafael J. Wysocki
2013-08-13 19:45 ` Rafael J. Wysocki
2013-08-13 21:09 ` Benjamin Herrenschmidt
2013-08-13 21:09 ` Benjamin Herrenschmidt
2013-08-13 21:09 ` Benjamin Herrenschmidt
2013-08-13 21:09 ` Benjamin Herrenschmidt
2013-08-14 9:23 ` Sudeep KarkadaNagesha
2013-08-14 9:23 ` Sudeep KarkadaNagesha
2013-08-14 9:23 ` Sudeep KarkadaNagesha
2013-08-13 21:08 ` Benjamin Herrenschmidt
2013-08-13 21:08 ` Benjamin Herrenschmidt
2013-08-13 21:08 ` Benjamin Herrenschmidt
2013-08-13 21:03 ` Benjamin Herrenschmidt
2013-08-13 21:03 ` Benjamin Herrenschmidt
2013-08-13 21:03 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5203BE15.2040506@arm.com \
--to=sudeep.karkadanagesha@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.