Linux Serial subsystem development
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: linux-kernel@vger.kernel.org, thierry.reding@avionic-design.de,
	gregkh@linuxfoundation.org,
	Laxman Dewangan <ldewangan@nvidia.com>,
	linux-serial@vger.kernel.org
Subject: Re: [PATCH 3/3] serial: tegra: Convert to devm_ioremap_resource()
Date: Thu, 31 Jan 2013 21:24:10 -0700	[thread overview]
Message-ID: <510B436A.20808@wwwdotorg.org> (raw)
In-Reply-To: <CAK9yfHzSq8SpKXQYtFd1Ds+N-AoH+H+BdWrPsPT=OwSPdst1WA@mail.gmail.com>

On 01/31/2013 09:20 PM, Sachin Kamat wrote:
> On 31 January 2013 22:30, Stephen Warren <swarren@wwwdotorg.org> wrote:
>> On 01/31/2013 03:25 AM, Sachin Kamat wrote:
>>> Use the newly introduced devm_ioremap_resource() instead of
>>> devm_request_and_ioremap() which provides more consistent error handling.
>>
>> Presumably though that function isn't yet available in the tree that
>> this new serial driver was merged through is it?
> 
> 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.

https://git.kernel.org/?p=linux/kernel/git/gregkh/tty.git;a=shortlog;h=refs/heads/tty-next

  reply	other threads:[~2013-02-01  4:24 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 [this message]
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
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=510B436A.20808@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