From: Greg KH <greg@kroah.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Greg KH <gregkh@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Kay Sievers <kay.sievers@vrfy.org>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
davem@davemloft.net
Subject: Re: [PATCH] PCI: make pci_name use dev_name
Date: Thu, 3 Jul 2008 13:52:05 -0700 [thread overview]
Message-ID: <20080703205205.GA17079@kroah.com> (raw)
In-Reply-To: <200807031333.56892.jbarnes@virtuousgeek.org>
On Thu, Jul 03, 2008 at 01:33:56PM -0700, Jesse Barnes wrote:
> On Thursday, July 03, 2008 1:24 pm Greg KH wrote:
> > On Thu, Jul 03, 2008 at 12:37:30PM -0700, Jesse Barnes wrote:
> > > On Wednesday, July 02, 2008 1:22 pm Greg KH wrote:
> > > > On Wed, Jul 02, 2008 at 09:04:22AM -0700, Greg KH wrote:
> > > > > Well, it's only used in 837 different places, so it might take me a
> > > > > few hours to ensure I catch all the usages :(
> > > >
> > > > Ok, here are 4 patches that fix the few places that this pci change
> > > > caused problems.
> > > >
> > > > Jesse, do you want to add these to your tree? I can take the single
> > > > USB one if you want, or you can take all 4, it's fine with me.
> > >
> > > I'd rather just take the PCI patch (which I'm doing now). The other
> > > stuff can come in through the appropriate tree.
> >
> > Fair enough, I'll make sure they don't get dropped.
>
> Cool thanks. I assume you'll only push the pci_name change once all or most
> of the compiler warnings have been fixed up?
As there were only 4 patches for the warnings, yes, I can handle that :)
thanks,
greg k-h
prev parent reply other threads:[~2008-07-03 20:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 15:35 [PATCH] PCI: make pci_name use dev_name Greg Kroah-Hartman
2008-07-02 15:51 ` Greg Kroah-Hartman
2008-07-02 15:58 ` Jesse Barnes
2008-07-02 16:04 ` Greg KH
2008-07-02 20:22 ` Greg KH
2008-07-02 20:24 ` [patch 01/04] MTD: handle pci_name() being const Greg Kroah-Hartman
2008-07-02 20:24 ` [patch 02/04] PCI: " Greg Kroah-Hartman
2008-07-03 19:33 ` Jesse Barnes
2008-07-02 20:24 ` [patch 03/04] 3c59x: " Greg Kroah-Hartman
2008-07-02 23:28 ` Andrew Morton
2008-07-03 12:17 ` Steffen Klassert
2008-07-03 15:43 ` Greg KH
2008-08-07 6:31 ` Jeff Garzik
2008-08-07 10:18 ` Steffen Klassert
2008-07-02 20:24 ` [patch 04/04] USB: " Greg Kroah-Hartman
2008-07-03 19:37 ` [PATCH] PCI: make pci_name use dev_name Jesse Barnes
2008-07-03 20:24 ` Greg KH
2008-07-03 20:33 ` Jesse Barnes
2008-07-03 20:52 ` Greg KH [this message]
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=20080703205205.GA17079@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=jbarnes@virtuousgeek.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--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