All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: David Dillow <dillowd@y12.doe.gov>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] IBM Lanstreamer bugfixes (round 3)
Date: Mon, 04 Mar 2002 14:12:55 -0500	[thread overview]
Message-ID: <3C83C737.397989BE@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0203041023580.11065-100000@janetreno.austin.ibm.com> <3C83A925.F93BF448@mandrakesoft.com> <3C83AE6B.9B5DE85F@y12.doe.gov> <3C83B2E7.B5EB0FB5@mandrakesoft.com> <3C83C0B8.659F1AE@y12.doe.gov> <3C83C258.FCF57746@mandrakesoft.com> <3C83C4B6.B7A95B5A@y12.doe.gov>

David Dillow wrote:
> Jeff Garzik wrote:
> > pci_enable_device doesn't touch PCI_COMMAND_INVALIDATE either, on most
> > platforms (particularly ia32, i.e. the popular one :))

> This seems to be a common thing to set; shouldn't we have a helper for
> it as well, or have pci_enable_device() do it?

Quoting my message to you from a couple hours ago:
> I need to create a pci_set_mwi() helper function.

	Jeff



-- 
Jeff Garzik      |
Building 1024    |
MandrakeSoft     | Choose life.

  reply	other threads:[~2002-03-04 19:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-15 21:44 [PATCH] IBM Lanstreamer bugfixes (round 3) Kent Yoder
2002-02-16 11:12 ` Jeff Garzik
2002-03-04 16:51   ` Kent Yoder
2002-03-04 17:04     ` Jeff Garzik
2002-03-04 17:27       ` David Dillow
2002-03-04 17:46         ` Jeff Garzik
2002-03-04 18:45           ` David Dillow
2002-03-04 18:52             ` Jeff Garzik
2002-03-04 19:02               ` David Dillow
2002-03-04 19:12                 ` Jeff Garzik [this message]
2002-03-04 18:58       ` Kent Yoder
2002-03-04 19:10         ` Jeff Garzik
2002-03-05 14:59           ` pjd
2002-03-05 15:37           ` Kent Yoder
  -- strict thread matches above, loose matches on Subject: below --
2002-02-04 17:16 Kent Yoder

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=3C83C737.397989BE@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=dillowd@y12.doe.gov \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.