From: Bart Van Assche <Bart.VanAssche@wdc.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"keescook@chromium.org" <keescook@chromium.org>,
"luc.vanoostenryck@gmail.com" <luc.vanoostenryck@gmail.com>
Cc: "mingo@kernel.org" <mingo@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Martin.Uecker@med.uni-goettingen.de"
<Martin.Uecker@med.uni-goettingen.de>,
"miguel.ojeda.sandonis@gmail.com"
<miguel.ojeda.sandonis@gmail.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] kernel.h: Avoid that sparse complains about using sizeof(void)
Date: Sun, 15 Jul 2018 03:28:03 +0000 [thread overview]
Message-ID: <efdfce609aebc2f583eb843acad2438dfdf9ec9f.camel@wdc.com> (raw)
In-Reply-To: <CA+55aFynusYJ8OCS_jnQhOEEjrfVhYV5PLxi_XF8ritsWEcP0A@mail.gmail.com>
On Sat, 2018-07-14 at 18:59 -0700, Linus Torvalds wrote:
> On Sat, Jul 14, 2018 at 6:57 PM Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> > Honestly, I'd like to just encourage people to get the sparse update
> > from Luc Van Oostenryck instead.
> >
> > For a while there it looked like Chris Li would just pull from Luc,
> > and we'd have timely releases, but that really doesn't seem to have
> > ended up happening after all. So right now it's probably just best to
> > get Luc's tree instead from
> >
> > https://github.com/lucvoo/sparse-dev
> >
> > which also ends up fixing a lot of other issues.
> >
> > Linus
>
> Oh,
> and I meant to cc Luc on that email, but then forgot. So here he is cc'd now.
>
> Linus
Hello everyone,
I will switch to Luc's sparse tree.
Thank you for the feedback.
Bart.
next prev parent reply other threads:[~2018-07-15 3:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 16:17 Bart Van Assche
2018-07-15 1:49 ` Kees Cook
2018-07-15 1:57 ` Linus Torvalds
2018-07-15 1:59 ` Linus Torvalds
2018-07-15 3:28 ` Bart Van Assche [this message]
2018-07-15 4:07 ` Bart Van Assche
2018-07-16 15:21 ` konstantin
2018-07-15 20:24 ` Luc Van Oostenryck
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=efdfce609aebc2f583eb843acad2438dfdf9ec9f.camel@wdc.com \
--to=bart.vanassche@wdc.com \
--cc=Martin.Uecker@med.uni-goettingen.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=mingo@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®