From: Christopher Li <sparse@chrisli.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Jeff Layton <jlayton@kernel.org>,
Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] build: clean up $CFLAGS handling in the makefile
Date: Sun, 5 Nov 2017 08:45:53 +0800 [thread overview]
Message-ID: <CANeU7Qm4+DWdcDrMytWqxTELrwuyMEkhs2hFGj6599ghetBE8A@mail.gmail.com> (raw)
In-Reply-To: <20171101141705.aqn5gnwvuohkapp3@ltop.local>
On Wed, Nov 1, 2017 at 10:17 PM, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
> This is still not correct. It still doesn't allow to compile sparse
> via 'make CFLAGS=<some extra flags, possibly none>'.
>
> Visibly this hasn't been tested.
Sorry about that.
There is one spot I miss after solving conflict of rebase master.
How about this one:
https://git.kernel.org/pub/scm/devel/sparse/chrisl/sparse.git/log/?h=cflags-v3
Thanks
Chris
next prev parent reply other threads:[~2017-11-05 0:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 10:02 [PATCH] build: clean up $CFLAGS handling in the makefile Jeff Layton
2017-10-25 14:20 ` Luc Van Oostenryck
2017-10-26 10:08 ` Christopher Li
2017-10-26 12:11 ` Jeff Layton
2017-10-26 17:11 ` Christopher Li
2017-10-29 11:32 ` Christopher Li
2017-10-29 17:28 ` Luc Van Oostenryck
2017-10-29 21:53 ` Christopher Li
2017-10-29 22:11 ` Josh Triplett
2017-10-29 22:48 ` Christopher Li
2017-10-30 5:40 ` Luc Van Oostenryck
2017-10-30 6:34 ` Christopher Li
2017-10-31 18:57 ` Jeff Layton
2017-11-01 0:56 ` Christopher Li
2017-11-01 14:17 ` Luc Van Oostenryck
2017-11-05 0:45 ` Christopher Li [this message]
2017-11-05 16:57 ` Luc Van Oostenryck
2017-11-09 21:10 ` Christopher Li
2017-11-09 21:26 ` Luc Van Oostenryck
2017-11-09 22:18 ` Christopher Li
2017-11-09 22:55 ` 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=CANeU7Qm4+DWdcDrMytWqxTELrwuyMEkhs2hFGj6599ghetBE8A@mail.gmail.com \
--to=sparse@chrisli.org \
--cc=jlayton@kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
/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).