From: luca abeni <luca.abeni@santannapisa.it>
To: Jakub Kicinski <kubakici@wp.pl>
Cc: Matthew Wilcox <willy@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Sparse warnings from sched.h
Date: Sun, 26 Nov 2017 11:46:42 +0100 [thread overview]
Message-ID: <20171126114642.494d86a9@sweethome> (raw)
In-Reply-To: <20171125214611.4238da3a@cakuba.netronome.com>
On Sat, 25 Nov 2017 21:46:11 -0800
Jakub Kicinski <kubakici@wp.pl> wrote:
> Hi!
>
> Did these:
>
> ./include/linux/sched.h:476:62: error: dubious one-bit signed bitfield
> ./include/linux/sched.h:477:62: error: dubious one-bit signed bitfield
> ./include/linux/sched.h:478:62: error: dubious one-bit signed bitfield
> ./include/linux/sched.h:479:62: error: dubious one-bit signed bitfield
>
> got fixed? I saw there were patches posted, but nothing have reached
> Linus's tree, yet.
I think a fix is in the tip tree:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=aa5222e92f8000ed3c1c38dddf11c83222aadfb3
Luca
prev parent reply other threads:[~2017-11-26 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-26 5:46 Sparse warnings from sched.h Jakub Kicinski
2017-11-26 10:46 ` Matthew Wilcox
2017-11-26 10:46 ` luca abeni [this message]
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=20171126114642.494d86a9@sweethome \
--to=luca.abeni@santannapisa.it \
--cc=dan.carpenter@oracle.com \
--cc=kubakici@wp.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=willy@infradead.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.