public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Thierry Reding <thierry.reding@avionic-design.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	USB list <linux-usb@vger.kernel.org>
Subject: Re: [GIT PATCH] USB patches for 3.9-rc1
Date: Thu, 21 Feb 2013 13:58:39 -0800	[thread overview]
Message-ID: <20130221215839.GB28131@kroah.com> (raw)
In-Reply-To: <CA+55aFwjbGRvGHhQQ7vUYP+wChp_ZBQ54ZFxzrRjTkdffcteWQ@mail.gmail.com>

On Thu, Feb 21, 2013 at 12:25:24PM -0800, Linus Torvalds wrote:
> On Thu, Feb 21, 2013 at 10:40 AM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > USB patches for 3.9-rc1
> >
> > Here's the big USB merge for 3.9-rc1
> >
> > Nothing major, lots of gadget fixes, and of course, xhci stuff.
> 
> Ok, so there were a couple of conflicts with Thierry Reding's series
> to convert devm_request_and_ioremap() users into
> devm_ioremap_resource(), where some of the old users had been
> converted to use other helper functions (eg omap_get_control_dev()).

That's fine.

> I left the omap_get_control_dev() users alone, but I do want to note
> that omap_control_usb_probe() itself now uses that
> devm_request_and_ioremap() function. And I did *not* extend the merge
> to do that kind of conversion in the helper function, so I'm assuming
> Thierry might want to extend his work. Assuming people care enough..

Yes, his plan was to do another sweep of the calls and hopefully remove
the old api in 3.10 or so once that is all cleaned up.

thanks,

greg k-h

  reply	other threads:[~2013-02-21 21:58 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-21 18:40 [GIT PATCH] USB patches for 3.9-rc1 Greg KH
2013-02-21 20:25 ` Linus Torvalds
2013-02-21 21:58   ` Greg KH [this message]
2013-02-22  6:47     ` Thierry Reding
2013-02-22  8:59 ` Dave Jones
2013-02-22  9:42   ` Lan Tianyu
2013-02-22  9:51   ` Lan Tianyu
2013-02-22 16:43     ` Dave Jones
2013-02-22 17:02       ` Lan Tianyu
2013-02-22 17:14         ` Dave Jones
2013-02-22 17:17           ` Lan Tianyu
2013-02-22 17:20             ` Dave Jones
2013-02-22 17:38               ` Lan Tianyu
2013-02-22 21:51   ` Fabio Baltieri
2013-02-22 22:23     ` Dave Jones
2013-02-23  0:10       ` Fabio Baltieri
2013-02-23  0:35         ` Rafael J. Wysocki
2013-02-23  1:44           ` Fabio Baltieri
2013-02-23  4:33             ` Rafael J. Wysocki
2013-02-23 11:49               ` Fabio Baltieri
2013-02-23 14:18                 ` [PATCH] ACPI / PM: Take unusual configurations of power resources into account (was: Re: [GIT PATCH] USB patches for 3.9-rc1) Rafael J. Wysocki
2013-02-23 14:48                   ` Fabio Baltieri
2013-02-23 22:29                     ` Rafael J. Wysocki
2013-02-23  0:20       ` [GIT PATCH] USB patches for 3.9-rc1 Rafael J. Wysocki
2013-02-23  0:19     ` Rafael J. Wysocki
2013-02-23  0:30       ` Linus Torvalds
2013-02-23  0:48         ` Rafael J. Wysocki
2013-02-23  1:10           ` Linus Torvalds
2013-02-23  2:01             ` Rafael J. Wysocki
2013-02-23  1:00     ` Rafael J. Wysocki

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=20130221215839.GB28131@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=thierry.reding@avionic-design.de \
    --cc=torvalds@linux-foundation.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