From: Dave Jones <davej@codemonkey.org.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Sebastian Benoit <benoit-lists@fb12.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: drivers/pci/quirks.c / Re: Linux v2.5.50
Date: Thu, 28 Nov 2002 17:31:20 +0000 [thread overview]
Message-ID: <20021128173120.GC930@suse.de> (raw)
In-Reply-To: <1038505301.10168.26.camel@irongate.swansea.linux.org.uk>
On Thu, Nov 28, 2002 at 05:41:41PM +0000, Alan Cox wrote:
> > It moves most obvious stuff (northbridges quirks) to the proper
> > place (arch/i386/pci/fixups.c).
> What about x86_64 ?
> Can the x86_64 folks verify these are not going to appear in x86_64
> systems at all ?
I would hope no-one has the idea to wire a hammer up to a
triton/natoma chipset. The VIA ones are more questionable.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-11-28 17:26 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 23:07 Linux v2.5.50 Linus Torvalds
2002-11-28 0:49 ` Udo A. Steinberg
2002-11-28 9:10 ` Gerd Knorr
2002-11-28 11:35 ` Gerd Knorr
2002-11-28 2:43 ` [uPATCH] NCR5380.c compile fix " Paul
2002-12-04 10:52 ` Geert Uytterhoeven
2002-11-28 4:55 ` [oops] BUG at mm/highmem.c:455 " Paul
2002-11-28 4:57 ` Nathan Walp
2002-11-28 10:15 ` drivers/pci/quirks.c / " Sebastian Benoit
2002-11-28 16:25 ` Alan Cox
2002-11-28 17:02 ` Ivan Kokshaysky
2002-11-28 17:30 ` Dave Jones
2002-11-28 18:54 ` Alan Cox
2002-11-28 18:25 ` Dave Jones
2002-11-28 18:30 ` Mike Dresser
2002-11-28 17:41 ` Alan Cox
2002-11-28 17:31 ` Dave Jones [this message]
2002-11-28 17:41 ` Ivan Kokshaysky
2002-11-28 13:17 ` Geert Uytterhoeven
2002-11-30 20:06 ` Adrian Bunk
2002-12-01 14:41 ` Adrian Bunk
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=20021128173120.GC930@suse.de \
--to=davej@codemonkey.org.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benoit-lists@fb12.de \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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