From: Randy Dunlap <rdunlap@infradead.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Christopher Li <sparse@chrisli.org>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH 0/2] fix missing evaluation when using '-include <file>'
Date: Wed, 14 Feb 2018 16:00:42 -0800 [thread overview]
Message-ID: <c4fc5ede-354e-e8db-92a6-232431c764d9@infradead.org> (raw)
In-Reply-To: <CAHmME9r9xfzFb02H_E8Ri_tTY9mO-cWBFxrxifZLTYQ_KVvDgQ@mail.gmail.com>
On 02/14/2018 04:15 AM, Jason A. Donenfeld wrote:
> Hi Christopher,
>
> Could you apply those two patches, and then afterwards, cut a 0.5.2 release?
>
> Thanks,
> Jason
It would be useful for continuous kernel build bots to have the
"ignore indirect_branch attribute" patch as well.
thanks,
--
~Randy
prev parent reply other threads:[~2018-02-15 0:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHmME9o--jumLrBbRn63ewKOE49+uYJ9B8V5FocptdwZ5Kd9Fw@mail.gmail.com>
2017-04-04 20:12 ` sparse with 4.10? Luc Van Oostenryck
[not found] ` <CAHmME9qu6p344M_VnubGtRYvbM7+w4kDmHGJG_PZvLK0kaheOw@mail.gmail.com>
2017-09-16 12:25 ` Jason A. Donenfeld
2017-09-16 14:33 ` Luc Van Oostenryck
2017-09-17 10:05 ` [PATCH 0/2] fix missing evaluation when using '-include <file>' Luc Van Oostenryck
2017-09-17 10:05 ` [PATCH 1/2] fix: missing evaluate with '-include' : add testcase Luc Van Oostenryck
2017-09-17 10:05 ` [PATCH 2/2] fix: missing evaluate with '-include' Luc Van Oostenryck
2017-09-17 11:59 ` [PATCH 0/2] fix missing evaluation when using '-include <file>' Jason A. Donenfeld
2017-09-17 19:02 ` Luc Van Oostenryck
2017-11-05 16:52 ` Luc Van Oostenryck
2018-01-30 13:23 ` Jason A. Donenfeld
2018-02-10 20:02 ` Luc Van Oostenryck
2018-02-13 23:49 ` Christopher Li
2018-02-14 0:02 ` Luc Van Oostenryck
2018-02-14 12:15 ` Jason A. Donenfeld
2018-02-15 0:00 ` Randy Dunlap [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=c4fc5ede-354e-e8db-92a6-232431c764d9@infradead.org \
--to=rdunlap@infradead.org \
--cc=Jason@zx2c4.com \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.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).