linux-kernel - Re: [patch 3/3] PCI: use dev_printk in x86 quirk messages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071221222956.GB24478@suse.de>
Date:	Fri, 21 Dec 2007 14:29:56 -0800
From:	Greg KH <gregkh@...e.de>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Ingo Molnar <mingo@...e.hu>, bjorn.helgaas@...com,
	tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
	dbrownell@...rs.sourceforge.net, linux-kernel@...r.kernel.org,
	linux-pci@...ey.karlin.mff.cuni.cz
Subject: Re: [patch 3/3] PCI: use dev_printk in x86 quirk messages

On Fri, Dec 21, 2007 at 01:47:35PM -0800, Andrew Morton wrote:
> On Tue, 18 Dec 2007 14:58:01 +0100
> Ingo Molnar <mingo@...e.hu> wrote:
> 
> > 
> > * bjorn.helgaas@...com <bjorn.helgaas@...com> wrote:
> > 
> > > Convert quirk printks to dev_printk().
> > 
> > thanks, applied the x86 bits.
> > 
> 
> Greg applied it too.  Could you guys please sort out some sort of
> who-owns-what protocol?
> 
> Thanks.
> 
> > 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.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/