mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Robert Richter <robert.richter@amd.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>,
	Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [osrc-patches] [PATCH] x86: Add PCI IDs for AMD Barcelona PCI devices
Date: Sat, 12 Jul 2008 06:56:15 +0200	[thread overview]
Message-ID: <20080712045615.GA11092@elte.hu> (raw)
In-Reply-To: <20080711124659.GC7963@erda.amd.com>


* Robert Richter <robert.richter@amd.com> wrote:

> Ingo, what about this patch. Could you apply it somewhere to the tip 
> tree? I will then fix all hardcoded device entries in the code.

i suspect we could do it if the include/linux/pci_ids.h modification is 
fine with Jesse - it appears the maintenance policy right now is for 
everyone to add to include/linux/pci_ids.h on an as-needed basis:

$ git-log-line linus..linux-next include/linux/pci_ids.h

# 1126de5: Merge commit 'mmc/next'
# bd3b052: Merge commit 'galak/powerpc-next'
# edf0e24: powerpc/85xx: Add support for MPC8536DS
# 34f80b0: bnx2x: Add support for BCM57711 HW
# d3bca0e: sdhci: support JMicron secondary interface
# 4ae127d: Merge branch 'master' of master.kernel.org:/pub/scm/linux/kernel/git/
# da65b53e4: Merge branch 'master' of master.kernel.org:/pub/scm/linux/kernel/git/
# da57e6983: tg3: Add 5785 ASIC revision

Which would normally go fine and not create conflicts because the 
modifications are distributed randomly over that file.

I'd suggest for you to send it together with the clean up patches, so 
that the context is clear.

	Ingo

> On 27.06.08 16:04:28, Robert Richter wrote:
> > Signed-off-by: Robert Richter <robert.richter@amd.com>
> > ---
> >  include/linux/pci_ids.h |    5 +++++
> >  1 files changed, 5 insertions(+), 0 deletions(-)
> > 
> > diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
> > index eafc9d6..4a2557c 100644
> > --- a/include/linux/pci_ids.h
> > +++ b/include/linux/pci_ids.h
> > @@ -497,6 +497,11 @@
> >  #define PCI_DEVICE_ID_AMD_K8_NB_ADDRMAP	0x1101
> >  #define PCI_DEVICE_ID_AMD_K8_NB_MEMCTL	0x1102
> >  #define PCI_DEVICE_ID_AMD_K8_NB_MISC	0x1103
> > +#define PCI_DEVICE_ID_AMD_10H_NB_HT	0x1200
> > +#define PCI_DEVICE_ID_AMD_10H_NB_MAP	0x1201
> > +#define PCI_DEVICE_ID_AMD_10H_NB_DRAM	0x1202
> > +#define PCI_DEVICE_ID_AMD_10H_NB_MISC	0x1203
> > +#define PCI_DEVICE_ID_AMD_10H_NB_LINK	0x1204
> >  #define PCI_DEVICE_ID_AMD_LANCE		0x2000
> >  #define PCI_DEVICE_ID_AMD_LANCE_HOME	0x2001
> >  #define PCI_DEVICE_ID_AMD_SCSI		0x2020
> > -- 
> > 1.5.5.4
> > 
> > _______________________________________________
> > osrc-patches mailing list
> > osrc-patches@elbe.amd.com
> > https://ddcwww.amd.com/mailman/listinfo/osrc-patches
> 
> -- 
> Advanced Micro Devices, Inc.
> Operating System Research Center
> email: robert.richter@amd.com

  reply	other threads:[~2008-07-12  4:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 14:04 Robert Richter
2008-06-27 22:15 ` Jeff Garzik
2008-06-30 10:44   ` Robert Richter
2008-07-11 12:46 ` [osrc-patches] " Robert Richter
2008-07-12  4:56   ` Ingo Molnar [this message]
2008-07-12  5:08     ` Arjan van de Ven
2008-07-14  9:15       ` Robert Richter
2008-07-14 15:54         ` Jesse Barnes

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=20080712045615.GA11092@elte.hu \
    --to=mingo@elte.hu \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robert.richter@amd.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

Powered by JetHome