Re: New and bogus(!) warning produced by sparse.

On Fri, 30 Sep 2005, Anton Altaparmakov wrote:
> 
> I just did a git pull on sparse and it produced a new and I believe 
> bogus warning when trying to assign a value to a bit field member.  The 
> warning is:

Thanks, that's indeed very bogus. 

I see why it happens, will fix sparse momentarily (btw, for sparse bugs, 
use "[email protected]" rather than LKML - since this is 
clearly not a kernel problem ;)

		Linus
-
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: New and bogus(!) warning produced by sparse.
    • From: Linus Torvalds <[email protected]>
  • Re: New and bogus(!) warning produced by sparse.
    • From: Linus Torvalds <[email protected]>

• References:
  • New and bogus(!) warning produced by sparse.
    • From: Anton Altaparmakov <[email protected]>

• Prev by Date: Re: I request inclusion of SAS Transport Layer and AIC-94xx into the kernel
• Next by Date: Re: [PATCH] cpuset crapectomy
• Previous by thread: New and bogus(!) warning produced by sparse.
• Next by thread: Re: New and bogus(!) warning produced by sparse.
• Index(es):
  • Date
  • Thread

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