From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Christopher Li <sparse@chrisli.org>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>,
Lance Richardson <lrichard@redhat.com>,
Johannes Berg <johannes@sipsolutions.net>
Subject: Re: [PATCH] sparse: update __builtin_object_size() prototype
Date: Thu, 17 Nov 2016 00:28:50 +0100 [thread overview]
Message-ID: <20161116232850.GB21402@macpro.local> (raw)
In-Reply-To: <CANeU7Q=hA2T+dgdi7cz_RK1Xday0g5PWszZMoT_Dw0vx0K5CBQ@mail.gmail.com>
On Thu, Nov 17, 2016 at 06:52:51AM +0800, Christopher Li wrote:
> On Mon, Nov 7, 2016 at 6:09 PM, Luc Van Oostenryck
> <luc.vanoostenryck@gmail.com> wrote:
> >
> > Acked-by: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
> >
> >
> > Chris, can you please take this patch (or Johannes' one).
> > When compiling the kernel, there is more than 2000 false warnings
> > only for the uaccess.h case described here above.
>
> Applied and pushed to "chrisl" repository.
>
> Thanks
>
> Chris
> --
Thanks.
BTW, how must we consider this "chrilsi" repository?
A bit like a -next repository or more like a working one?
Can we consider it as stable for git fetches & pulls?
Luc
next prev parent reply other threads:[~2016-11-16 23:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-21 14:13 [PATCH] sparse: update __builtin_object_size() prototype Lance Richardson
2016-11-07 10:09 ` Luc Van Oostenryck
2016-11-16 22:52 ` Christopher Li
2016-11-16 23:28 ` Luc Van Oostenryck [this message]
2016-11-17 8:28 ` Christopher Li
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=20161116232850.GB21402@macpro.local \
--to=luc.vanoostenryck@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-sparse@vger.kernel.org \
--cc=lrichard@redhat.com \
--cc=sparse@chrisli.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;
as well as URLs for NNTP newsgroup(s).