From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: linux1394-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
Jesse Barnes <jbarnes@virtuousgeek.org>,
bcollins@debian.org, Greg KH <greg@kroah.com>,
scjody@steamballoon.com, gregkh@suse.de
Subject: Re: new PCI quirk for Toshiba Satellite?
Date: Tue, 25 Oct 2005 01:09:01 +0400 [thread overview]
Message-ID: <20051025010901.B1661@jurassic.park.msu.ru> (raw)
In-Reply-To: <435D2612.5070701@s5r6.in-berlin.de>; from stefanr@s5r6.in-berlin.de on Mon, Oct 24, 2005 at 08:21:06PM +0200
On Mon, Oct 24, 2005 at 08:21:06PM +0200, Stefan Richter wrote:
> Once the workaround is in pci/quirks.c, a single #ifdef would suffice
> (if it is still of any benefit there).
Such an obviously i386-specific quirk should go into
arch/i386/pci/fixup.c.
Ivan.
next prev parent reply other threads:[~2005-10-24 21:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-15 18:55 ohci1394 unhandled interrupts bug in 2.6.14-rc2 jbarnes
2005-10-15 19:39 ` Stefan Richter
2005-10-15 20:29 ` Jesse Barnes
2005-10-15 20:40 ` new PCI quirk for Toshiba Satellite? Jesse Barnes
2005-10-20 0:06 ` Greg KH
2005-10-20 18:32 ` Stefan Richter
2005-10-21 18:38 ` Jesse Barnes
2005-10-21 20:13 ` Stefan Richter
2005-10-24 17:45 ` Jesse Barnes
2005-10-24 18:07 ` Jesse Barnes
2005-10-24 18:21 ` Stefan Richter
2005-10-24 21:09 ` Ivan Kokshaysky [this message]
2005-10-15 21:02 ` ohci1394 unhandled interrupts bug in 2.6.14-rc2 Stefan Richter
2005-10-15 21:59 ` Jesse Barnes
2005-10-17 7:55 ` Andrew Morton
2005-10-17 9:35 ` Stefan Richter
2005-10-17 9:42 ` Andrew Morton
2005-10-17 10:03 ` Stefan Richter
2005-10-17 16:30 ` Jesse Barnes
2005-10-17 18:50 ` Stefan Richter
2005-10-19 17:54 ` Jesse Barnes
2005-10-17 12:48 ` rob
2005-10-17 15:58 ` Stefan Richter
2005-10-18 5:32 ` rob
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=20051025010901.B1661@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=bcollins@debian.org \
--cc=greg@kroah.com \
--cc=gregkh@suse.de \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=scjody@steamballoon.com \
--cc=stefanr@s5r6.in-berlin.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®