mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Robert Richter <robert.richter@amd.com>,
	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: Fri, 11 Jul 2008 22:08:37 -0700	[thread overview]
Message-ID: <20080711220837.21f7d24a@infradead.org> (raw)
In-Reply-To: <20080712045615.GA11092@elte.hu>

On Sat, 12 Jul 2008 06:56:15 +0200
Ingo Molnar <mingo@elte.hu> wrote:

> 
> * 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.

actually lately for most cases it seems the plan isn't to add to
pci_ids.h, but just do the PCI ID directly. It's not like a #define
adds any kind of information.
Vendor ID's otoh still happen (but obviously AMD is there since
forever.)



-- 
If you want to reach me at my work email, use arjan@linux.intel.com
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2008-07-12  5:08 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
2008-07-12  5:08     ` Arjan van de Ven [this message]
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=20080711220837.21f7d24a@infradead.org \
    --to=arjan@infradead.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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

all inboxes | Powered by JetHome®