From: Jeff Garzik <jgarzik@pobox.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: David Brownell <david-b@pacbell.net>,
Anton Blanchard <anton@samba.org>,
linux-kernel@vger.kernel.org
Subject: Re: pci_set_mwi() ... why isn't it used more?
Date: Thu, 30 Jan 2003 19:11:55 -0500 [thread overview]
Message-ID: <3E39BF4B.2010000@pobox.com> (raw)
In-Reply-To: <20030131023419.A652@localhost.park.msu.ru>
Ivan Kokshaysky wrote:
> Thoughts?
Seems sane to me... I agree it's aggressive, because you're changing
behavior of pci_set_master(). But given that the MWI stuff in pci.c is
so new, I think that's probably ok.
next prev parent reply other threads:[~2003-01-31 0:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-20 18:41 pci_set_mwi() ... why isn't it used more? David Brownell
2003-01-20 19:00 ` Jeff Garzik
2003-01-20 19:37 ` David Brownell
2003-01-30 13:52 ` Anton Blanchard
2003-01-30 16:25 ` David Brownell
2003-01-30 16:59 ` Ivan Kokshaysky
2003-01-30 18:35 ` David Brownell
2003-01-30 23:34 ` Ivan Kokshaysky
2003-01-31 0:11 ` Jeff Garzik [this message]
2003-01-31 0:51 ` David Brownell
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=3E39BF4B.2010000@pobox.com \
--to=jgarzik@pobox.com \
--cc=anton@samba.org \
--cc=david-b@pacbell.net \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.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