All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: dougthompson@xmission.com
Cc: alan@lxorguk.ukuu.org.uk, linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 4/6] include linux pci_id-h add amd northbridge defines
Date: Mon, 11 Jun 2007 16:49:47 -0700	[thread overview]
Message-ID: <20070611234947.GA20078@kroah.com> (raw)
In-Reply-To: <963615.80973.qm@web50105.mail.re2.yahoo.com>

On Mon, Jun 11, 2007 at 04:30:11PM -0700, Doug Thompson wrote:
> 
> --- Greg KH <greg@kroah.com> wrote:
> 
> > On Fri, Jun 08, 2007 at 10:45:10AM -0600, dougthompson@xmission.com wrote:
> > > From:	Douglas Thompson <dougthompson@xmission.com>
> > > 
> > > pci_ids.h needs two of the AMD NB device-ids namely,
> > > Addressmap and the Memory Controller devices
> > 
> > Does any kernel driver need this?  We're trying to only include things
> > in the pci_ids.h file that are needed in more than one file to cut down
> > on the churn here for unnecessary ids.
> 
> not at the moment, but I have the k8_edac.c EDAC driver in my queue, which was in the -mm tree but
> I had to pull it back once.
> 
> I am working with the k8 driver and its dealing with a race with the mcelog device as both access
> the K8 NB. The K8 driver does use these regs and it currently has #ifndef s in it for both of
> them.
> 
> I guess I could have submitted the patch when the K8 driver was submitted.

That would be preferable, thanks.

greg k-h

  reply	other threads:[~2007-06-11 23:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-08 16:45 [PATCH 4/6] include linux pci_id-h add amd northbridge defines dougthompson
2007-06-09  0:08 ` Greg KH
2007-06-11 23:30   ` Doug Thompson
2007-06-11 23:49     ` Greg KH [this message]
2007-06-12  3:25       ` Dave Jones
2007-06-13  5:10         ` Doug Thompson
2007-06-13 12:44           ` 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=20070611234947.GA20078@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@osdl.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dougthompson@xmission.com \
    --cc=linux-kernel@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 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.