From: Stephen Warren <swarren@wwwdotorg.org>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: Sachin Kamat <sachin.kamat@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"thierry.reding@avionic-design.de"
<thierry.reding@avionic-design.de>,
Laxman Dewangan <ldewangan@nvidia.com>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: [PATCH 3/3] serial: tegra: Convert to devm_ioremap_resource()
Date: Fri, 15 Mar 2013 11:14:01 -0600 [thread overview]
Message-ID: <514356D9.2020708@wwwdotorg.org> (raw)
In-Reply-To: <20130315163803.GA29113@kroah.com>
On 03/15/2013 10:38 AM, gregkh@linuxfoundation.org wrote:
> On Sat, Feb 02, 2013 at 10:22:16AM +0530, Sachin Kamat wrote:
>>
>>
>> On Friday, 1 February 2013, Stephen Warren <swarren@wwwdotorg.org> wrote:
>>> On 02/01/2013 02:49 AM, Sachin Kamat wrote:
>>>> On 1 February 2013 09:54, Stephen Warren <swarren@wwwdotorg.org> wrote:
>>>>>>
>>>>>> The entire series is merged in Greg's driver-core tree [1] and I
>>>>>> presume all other associated patches would also be picked up by him.
>>>>>> Isn't it Greg?
>>>>>>
>>>>>> [1] git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git
>>>>>
>>>>> The Tegra serial driver went through Greg's TTY tree. I assume that goes
>>>>> direct to Linus not through driver-core.git first.
>>>>
>>>> Right. But AFAIK for this specific change he has carried the patches
>>>> in the device-core tree irrespective of the subsystem.
>>>
>>> Yes, but the Tegra serial driver is new for 3.9, and hence does not yet
>>> exist in driver-core.git.
>>>
>>
>> Oh ok. Then probably we can have this patch only after 3.9-rc1 is out.
>
> Yes, Stephen can take this patch now.
There's no need for me to take the patch I think; now that 3.9-rc1 is
out, the serial and driver core trees all have whatever dependencies
this series needed, so any patches can go through their usual trees, I
think... (Sorry, the context of this discussion was little while ago).
next prev parent reply other threads:[~2013-03-15 17:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1359627939-2685-1-git-send-email-sachin.kamat@linaro.org>
2013-01-31 10:25 ` [PATCH 3/3] serial: tegra: Convert to devm_ioremap_resource() Sachin Kamat
2013-01-31 17:00 ` Stephen Warren
2013-02-01 4:20 ` Sachin Kamat
2013-02-01 4:24 ` Stephen Warren
2013-02-01 9:49 ` Sachin Kamat
2013-02-01 17:18 ` Stephen Warren
[not found] ` <CAK9yfHx1jLPpdCHAb-pC-C7wt81gQLgTnpuvK+0aNKkhuXHcDQ@mail.gmail.com>
2013-03-15 16:38 ` gregkh
2013-03-15 17:14 ` Stephen Warren [this message]
2013-03-15 17:33 ` gregkh
2013-03-18 5:57 ` Sachin Kamat
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=514356D9.2020708@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=gregkh@linuxfoundation.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sachin.kamat@linaro.org \
--cc=thierry.reding@avionic-design.de \
/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