From: Greg KH <gregkh@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
bjorn.helgaas@hp.com, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, dbrownell@users.sourceforge.net,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [patch 3/3] PCI: use dev_printk in x86 quirk messages
Date: Fri, 21 Dec 2007 15:06:18 -0800 [thread overview]
Message-ID: <20071221230618.GA16365@suse.de> (raw)
In-Reply-To: <20071221224053.GA23289@elte.hu>
On Fri, Dec 21, 2007 at 11:40:53PM +0100, Ingo Molnar wrote:
>
> * Greg KH <gregkh@suse.de> wrote:
>
> > > > arch/x86/kernel/quirks.c | 42 ++++++++++++++++++++++--------------------
> > > > arch/x86/pci/fixup.c | 22 +++++++++++-----------
> > >
> > > That made it hard. Arguably one file is PCI tree and the other is
> > > x86 tree.
> >
> > Hm, as traditionally we haven't had such an active x86 maintainer,
> > I've handled most of the pci quirk type stuff that people have sent to
> > me in the past :)
> >
> > But, now that we have more enthusiastic developers, I can change this.
> > If you want me to cut portions of the patch up, I'll be glad to do so,
> > just let me know.
> >
> > It's easy for me when merging, as our tools can handle it just fine,
> > but Andrew is the one with the big problems, so we should probably
> > shake it out on our end first...
> >
> > Ingo, what is easiest for you to do? As I use quilt, I can very
> > simply cut a portion of the patch up, or drop it entirely.
>
> There's one patch right now in x86.git that affects
> arch/x86/kernel/quirks.c and arch/x86/pci/fixup.c - the one from Bjorn.
> (find below)
That's the same one I have :)
> Are your quirks (and other arch/x86) patches nicely standalone? If yes
> then we could pick them up just fine - patch-bomb me or send a tarball
> or mbox of the patches - whichever is the most convenient for you. (we
> too use quilt as the main repository)
They are usually mixed up with the other pci patches in my pci tree:
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/gregkh-02-pci/
> but if there's some dependency on continuing pci/driver infrastructure
> you might be working on then it would be better for you to carry them.
> Or if you'd just like to have Bjorn's patch in one piece. Tell me and
> i'll drop the changes below from x86.git.
>
> In any case, both variants would be fine for us - the important thing is
> to not drop any of the patches on the floor :)
How about you drop this one patch, and I'll keep it, as it goes along
with the other 2 patches in his series, and I'll make sure to check if I
have future pci quirk patches that affect the x86/ directory.
Sound reasonable?
thanks,
greg k-h
next prev parent reply other threads:[~2007-12-21 23:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-17 21:09 [patch 0/3] use dev_printk in PCI quirks bjorn.helgaas
2007-12-17 21:09 ` [patch 1/3] PCI: print quirk name in debug messages bjorn.helgaas
2007-12-17 21:09 ` [patch 2/3] PCI: use dev_printk in quirk messages bjorn.helgaas
2007-12-17 21:09 ` [patch 3/3] PCI: use dev_printk in x86 " bjorn.helgaas
2007-12-18 13:58 ` Ingo Molnar
2007-12-21 21:47 ` Andrew Morton
2007-12-21 22:29 ` Greg KH
2007-12-21 22:40 ` Ingo Molnar
2007-12-21 23:06 ` Greg KH [this message]
2007-12-22 2:10 ` Ingo Molnar
2008-01-22 17:45 ` Bjorn Helgaas
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=20071221230618.GA16365@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=dbrownell@users.sourceforge.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).