All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: bjorn.helgaas@hp.com, tglx@linutronix.de, mingo@redhat.com,
	hpa@zytor.com, gregkh@suse.de, 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 13:47:35 -0800	[thread overview]
Message-ID: <20071221134735.1e0066c9.akpm@linux-foundation.org> (raw)
In-Reply-To: <20071218135801.GB17470@elte.hu>

On Tue, 18 Dec 2007 14:58:01 +0100
Ingo Molnar <mingo@elte.hu> wrote:

> 
> * bjorn.helgaas@hp.com <bjorn.helgaas@hp.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.

  reply	other threads:[~2007-12-21 21:50 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 [this message]
2007-12-21 22:29       ` Greg KH
2007-12-21 22:40         ` Ingo Molnar
2007-12-21 23:06           ` Greg KH
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=20071221134735.1e0066c9.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=dbrownell@users.sourceforge.net \
    --cc=gregkh@suse.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.