Re: [PATCH 1/2] [PCI] Check that MWI bit really did get set

On Sunday 15 October 2006 6:10 pm, Andrew Morton wrote:

> - A printk if something went bad

Where "bad" would I hope exclude cases where the device
doesn't support MWI ... that is, the "go faster if you can"
advice from the driver, where it isn't an error to run into
the common case of _this_ implementation not happening to
be able to issue MWI cycles.

The other cases, where something actually went wrong, would
be reasonable for emitting KERN_ERR or KERN_WARNING messages.

- Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [PATCH 1/2] [PCI] Check that MWI bit really did get set
    • From: Matthew Wilcox <[email protected]>
  • Re: [PATCH 1/2] [PCI] Check that MWI bit really did get set
    • From: Paul Mackerras <[email protected]>
  • Re: [PATCH 1/2] [PCI] Check that MWI bit really did get set
    • From: Andrew Morton <[email protected]>

• Prev by Date: Re: root MD array is still in use upon shutdown possible fix
• Next by Date: Inspiron 6000 and CPU power saving
• Previous by thread: Re: [PATCH 1/2] [PCI] Check that MWI bit really did get set
• Next by thread: Re: [PATCH 1/2] [PCI] Check that MWI bit really did get set
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]