Re: MSI: Use correct data offset for 32-bit MSI in read_msi_msg()

Roland Dreier <[email protected]> writes:

>  > Well it is a bug worth fixing.  Who knows it may have something
>  > to do with the disable_irq problems the forcedeth driver was seeing.
>
> I agree completely, the fix looks obvious and there's no point in
> leaving the bug there.  I just don't have a test case that I can point
> to as being fixed by this, since I don't have a working 32-bit MSI
> device...
>
> Do you know whether the forcedeth devices have a 32-bit MSI address?

Sorry I don't.  The ones I have don't have an MSI capability.


Eric
-
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:
  • Re: MSI: Use correct data offset for 32-bit MSI in read_msi_msg()
    • From: [email protected] (Eric W. Biederman)
  • Re: MSI: Use correct data offset for 32-bit MSI in read_msi_msg()
    • From: Roland Dreier <[email protected]>
  • Re: MSI: Use correct data offset for 32-bit MSI in read_msi_msg()
    • From: [email protected] (Eric W. Biederman)
  • Re: MSI: Use correct data offset for 32-bit MSI in read_msi_msg()
    • From: Roland Dreier <[email protected]>

• Prev by Date: [PATCH 3/8] scsi: megaraid_sas - add module param max_sectors, cmd_per_lun
• Next by Date: [PATCH 4/8] scsi: megaraid_sas - check max_sgl reported by FW for setting max_sectors_per_req
• Previous by thread: Re: MSI: Use correct data offset for 32-bit MSI in read_msi_msg()
• Next by thread: strange bug with ip multicasting.
• 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]