linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Greg KH <greg@kroah.com>
Cc: Felipe Balbi <balbi@ti.com>,
	Jesse Barnes <jbarnes@virtuousgeek.org>,
	linux-pci@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>
Subject: Re: [PATCH] DWC3: use module_pci_driver
Date: Fri, 18 Nov 2011 21:22:22 +0200	[thread overview]
Message-ID: <20111118192220.GC11736@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <20111118191117.GA25016@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 780 bytes --]

On Fri, Nov 18, 2011 at 11:11:17AM -0800, Greg KH wrote:
> On Fri, Nov 18, 2011 at 09:04:14PM +0200, Felipe Balbi wrote:
> > Hi,
> > 
> > On Fri, Nov 18, 2011 at 10:14:24AM -0800, Greg KH wrote:
> > > From: Greg Kroah-Hartman <gregkh@suse.de>
> > > 
> > > This cuts down on the boilerplate code.
> > > 
> > > 
> > > Cc: Lars-Peter Clausen <lars@metafoo.de>
> > > Cc: Felipe Balbi <balbi@ti.com>
> > > Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
> > 
> > Looks good to me. It would be nice to see a similar patch for
> > dwc3-omap.c moving the platform_driver_register to this new macro :-)
> 
> We already have a platform driver macro in the tree, feel free to move
> it to use it now if you want :)

great, will do for 3.3 merge window.

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2011-11-18 19:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-18 18:12 [PATCH] PCI: Add helper macro for pci_register_driver boilerplate Greg KH
2011-11-18 18:14 ` [PATCH] DWC3: use module_pci_driver Greg KH
2011-11-18 19:04   ` Felipe Balbi
2011-11-18 19:11     ` Greg KH
2011-11-18 19:22       ` Felipe Balbi [this message]
2011-12-05 18:28 ` [PATCH] PCI: Add helper macro for pci_register_driver boilerplate Jesse Barnes
2011-12-05 18:38   ` Greg KH

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=20111118192220.GC11736@legolas.emea.dhcp.ti.com \
    --to=balbi@ti.com \
    --cc=greg@kroah.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=lars@metafoo.de \
    --cc=linux-pci@vger.kernel.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).