RE: [PATCH 1/1] aacraid: don't assign cpu_to_le32(int) to u8

Christoph Hellwig [mailto:[email protected]] sez:
> Did anyone run the driver through sparse to see if we have 
> more issues like this?

There are some warnings from sparse, none like this one. I will deal
with the warnings ...

Sincerely -- Mark Salyzyn

-
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/

---

• Follow-Ups:
  • Re: [PATCH 1/1] aacraid: don't assign cpu_to_le32(int) to u8
    • From: Christoph Hellwig <[email protected]>

• References:
  • Re: [PATCHv2] aacraid: don't assign cpu_to_le32(constant) to u8
    • From: Andreas Schwab <[email protected]>
  • [PATCH 1/1] aacraid: don't assign cpu_to_le32(int) to u8
    • From: "Salyzyn, Mark" <[email protected]>
  • Re: [PATCH 1/1] aacraid: don't assign cpu_to_le32(int) to u8
    • From: Christoph Hellwig <[email protected]>

• Prev by Date: Re: [PATCH] fix incorrect test in trident_ac97_set(); sound/oss/trident.c
• Next by Date: Re: [patch 04/23] dentries: Extract common code to remove dentry from lru
• Previous by thread: Re: [PATCH 1/1] aacraid: don't assign cpu_to_le32(int) to u8
• Next by thread: Re: [PATCH 1/1] aacraid: don't assign cpu_to_le32(int) to u8
• 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]