linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 12 Aug 2013 14:06:08 +0100	[thread overview]
Message-ID: <5208DDC0.9020601@arm.com> (raw)
In-Reply-To: <1518689.GpqxbJSNzp@vostro.rjw.lan>

On 12/08/13 14:13, Rafael J. Wysocki wrote:
> On Monday, August 12, 2013 01:41:58 PM Sudeep KarkadaNagesha wrote:
>> Hi Rafael,
>>
>> On 12/08/13 12:51, Rafael J. Wysocki wrote:
>>> On Monday, August 12, 2013 02:33:32 PM Viresh Kumar wrote:
>>>> On 12 August 2013 14:24, Sudeep KarkadaNagesha
>>>> <Sudeep.KarkadaNagesha@arm.com> wrote:
>>>>> Can you please let which know which branch do you prefer to base the my
>>>>> request on ?
>>>>
>>>> Unless you have any dependencies, you must rebase on latest RC..
>>>
>>> Yes, preferably 3.11-rc5.
>>>
>>> If there are any dependencies on linux-next material, please let me know.
>>>
>>
>> It doesn't have any functional dependencies, however I just found out
>> now that there's a conflict with today's linux-next branch(tag:
>> next-20130812)
> 
> That's not a big deal.
> 
Thanks Rafael, in that case I will send the pull request based on 3.11-rc5

Regards,
Sudeep

  reply	other threads:[~2013-08-12 13:06 UTC|newest]

Thread overview: 29+ 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
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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-08-12 13:27 Sudeep KarkadaNagesha
2013-08-13 13:00 ` Rafael J. Wysocki
2013-08-13 15:40   ` Sudeep KarkadaNagesha
2013-08-13 18:29     ` Sudeep KarkadaNagesha
2013-08-13 21:07       ` Benjamin Herrenschmidt
2013-08-14 10:01         ` Sudeep KarkadaNagesha
2013-08-14 11:37           ` Benjamin Herrenschmidt
2013-08-14 13:21             ` Sudeep KarkadaNagesha
2013-08-14 22:57               ` Benjamin Herrenschmidt
2013-08-14 12:53           ` Rob Herring
2013-08-14 13:27             ` Sudeep KarkadaNagesha
2013-08-13 18:37     ` Michal Simek
2013-08-14  8:41       ` Sudeep KarkadaNagesha
2013-08-13 18:44     ` Rob Herring
2013-08-13 19:45       ` Rafael J. Wysocki
2013-08-13 21:09         ` Benjamin Herrenschmidt
2013-08-14  9:23         ` Sudeep KarkadaNagesha
2013-08-13 21:08       ` 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=5208DDC0.9020601@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).