public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: david.gaarenstroom@gmail.com
Cc: linux-kernel@vger.kernel.org, jeff@garzik.org,
	barkalow@iabervon.org, linas@austin.ibm.com,
	chunhao.huang@hotmail.com, gregkh@suse.de, htejun@gmail.com,
	brice.goglin@gmail.com, linux-pci@atrey.karlin.mff.cuni.cz,
	shane.huang@amd.com, linux-ide@vger.kernel.org, brice@myri.com,
	mchan@broadcom.com
Subject: Re: [PATCH 5/5]: [PCI]: Remove 3 incorrect MSI quirks.
Date: Fri, 26 Oct 2007 04:38:33 -0700 (PDT)	[thread overview]
Message-ID: <20071026.043833.88113848.davem@davemloft.net> (raw)
In-Reply-To: <9783dadb0710260356g4ef94e3dvadf69d4d263c2361@mail.gmail.com>

From: "David Gaarenstroom" <david.gaarenstroom@gmail.com>
Date: Fri, 26 Oct 2007 12:56:52 +0200

> 2007/10/25, David Miller <davem@davemloft.net>:
> >
> > Now that we have dealt with the real issue, in that some ATI SATA and
> > USB controllers needed the INTX_DISABLE quirk, we can remove these AMD
> > chipset global MSI disabling quirks.
> 
> IMHO we should remove *all* former ATI "AMD" chipset global MSI
> disabling quirks... The whole idea was to sort things out once and for
> all. At least the RS480 quirk can be removed, now that the USB driver
> has the workaround for the SB400 southbridge USB. I suspect the same
> counts for the other ATI chipsets...

I would like those to be removed, but to be conservative we should
first get some testing feedback that confirms this just like those
provided to me from the AMD folks for the RS690, RX790 and RD580
cases.

Otherwise the risk to break people's systems is very real.

  reply	other threads:[~2007-10-26 11:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25  8:17 [PATCH 5/5]: [PCI]: Remove 3 incorrect MSI quirks David Miller
2007-10-26 10:56 ` David Gaarenstroom
2007-10-26 11:38   ` David Miller [this message]
2007-10-28 20:11     ` David Gaarenstroom
2007-10-29  1:08       ` David Miller
2007-10-29  6:06     ` Shane Huang
2007-10-29  6:13       ` Tejun Heo

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=20071026.043833.88113848.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=barkalow@iabervon.org \
    --cc=brice.goglin@gmail.com \
    --cc=brice@myri.com \
    --cc=chunhao.huang@hotmail.com \
    --cc=david.gaarenstroom@gmail.com \
    --cc=gregkh@suse.de \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=linas@austin.ibm.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=mchan@broadcom.com \
    --cc=shane.huang@amd.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