From: Greg KH <greg@kroah.com>
To: David Miller <davem@davemloft.net>
Cc: Shane.Huang@amd.com, david.gaarenstroom@gmail.com,
linux-kernel@vger.kernel.org, linas@austin.ibm.com,
gregkh@suse.de, htejun@gmail.com, brice.goglin@gmail.com,
linux-pci@atrey.karlin.mff.cuni.cz, jgarzik@pobox.com
Subject: Re: [patch] PCI: disable MSI on more ATI NorthBridges
Date: Tue, 23 Oct 2007 23:53:54 -0700 [thread overview]
Message-ID: <20071024065354.GA15916@kroah.com> (raw)
In-Reply-To: <20071023.194155.112293423.davem@davemloft.net>
On Tue, Oct 23, 2007 at 07:41:55PM -0700, David Miller wrote:
> From: "Shane Huang" <Shane.Huang@amd.com>
> Date: Tue, 23 Oct 2007 18:56:03 +0800
>
> > Also I wonder why the USB MSI patch is not added into kernel at last?
> > Will it lead to other bugs?
>
> Probably someone just needs to be more vocal and active in pushing it
> to the USB subsystem maintainer(s). I've even had trouble getting
> even simple bug fixes integrated recently, so perhaps it will take a
> few retransmits and some patience to get it included.
Yeah, I appologize for some of our developers, they seem a bit grumpy at
times :(
> Greg, can you at least devote a few minutes to going over that USB MSI
> patch, giving it any obvious things it needs (perhaps some
> pci_msi_enable() return value checks, for example, but may not be
> needed at all in this case) and then stash it somewhere so it doesn't
> get lost in the void?
Can someone forward it to me so that I can see it? I can't seem to
locate it at the moment, was I copied on it?
thanks,
greg k-h
next prev parent reply other threads:[~2007-10-24 6:55 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 13:17 [patch] PCI: disable MSI on more ATI NorthBridges Shane Huang
[not found] ` <9783dadb0710190706i499b4edbh9736019b0384f9b1@mail.gmail.com>
2007-10-19 14:10 ` Fwd: " David Gaarenstroom
2007-10-19 19:57 ` Linas Vepstas
2007-10-19 20:21 ` Jeff Garzik
2007-10-20 22:03 ` Benjamin Herrenschmidt
2007-10-22 20:26 ` Daniel Barkalow
2007-10-22 20:41 ` Jeff Garzik
2007-10-22 21:31 ` Daniel Barkalow
2007-10-22 23:48 ` Krzysztof Halasa
2007-10-23 0:13 ` David Miller
2007-10-23 5:52 ` Daniel Barkalow
2007-10-23 9:39 ` Shane Huang
2007-10-23 10:01 ` Jeff Garzik
2007-10-23 10:06 ` David Miller
2007-10-24 2:46 ` David Miller
2007-10-23 10:15 ` Jeff Garzik
2007-10-22 23:40 ` Krzysztof Halasa
2007-10-22 23:58 ` David Miller
2007-10-23 10:13 ` Jeff Garzik
2007-10-20 14:50 ` Shane Huang
2007-10-20 20:52 ` David Gaarenstroom
2007-10-21 6:00 ` Shane Huang
2007-10-23 10:56 ` Shane Huang
2007-10-24 2:41 ` David Miller
2007-10-24 6:53 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-18 9:14 Shane Huang
2007-10-18 10:19 ` David Miller
2007-10-18 10:37 ` Shane Huang
2007-10-18 11:46 ` David Miller
2007-10-18 15:24 ` Greg KH
2007-10-19 17:42 ` Daniel Barkalow
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=20071024065354.GA15916@kroah.com \
--to=greg@kroah.com \
--cc=Shane.Huang@amd.com \
--cc=brice.goglin@gmail.com \
--cc=davem@davemloft.net \
--cc=david.gaarenstroom@gmail.com \
--cc=gregkh@suse.de \
--cc=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linas@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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