From: Jeff Garzik <jeff@garzik.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Daniel Barkalow <barkalow@iabervon.org>,
gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: Disable INTx when enabling MSI
Date: Thu, 07 Dec 2006 17:53:12 -0500 [thread overview]
Message-ID: <45789B58.8090307@garzik.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0612071440480.3615@woody.osdl.org>
Linus Torvalds wrote:
>
> On Thu, 7 Dec 2006, Daniel Barkalow wrote:
>> Jeff proposed a patch in http://lkml.org/lkml/2006/11/21/332 when Linus
>> wanted to do it in the PCI layer, but nobody seems to have told the actual
>> PCI maintainer.
>
> I got a patch from Jeff, but it was marked as totally untested, and wasn't
> even signed-off, so I asked for that to be fixed, and never heard back.
>
> If somebody sends me the patch that disables INTx when MSI is enabled,
> with testing, and saying "I verified that this fixed it for me", I will
> happily apply it.
Making it now...
Jeff
prev parent reply other threads:[~2006-12-07 22:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 22:31 Disable INTx when enabling MSI Daniel Barkalow
2006-12-07 22:39 ` Greg KH
2006-12-07 23:04 ` Daniel Barkalow
2006-12-07 22:44 ` Linus Torvalds
2006-12-07 22:53 ` Jeff Garzik [this message]
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=45789B58.8090307@garzik.org \
--to=jeff@garzik.org \
--cc=barkalow@iabervon.org \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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