From: Sam Ravnborg <sam@ravnborg.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: "Robert P. J. Day" <rpjday@mindspring.com>,
linux-kbuild@vger.kernel.org,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kbuild: sparse needs CF not CHECKFLAGS
Date: Fri, 27 Jun 2008 23:07:27 +0200 [thread overview]
Message-ID: <20080627210727.GD29245@uranus.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0806201542200.27182@vixen.sonytel.be>
On Fri, Jun 20, 2008 at 03:45:12PM +0200, Geert Uytterhoeven wrote:
> Documentation/sparse.txt tells to use:
>
> make C=2 CHECKFLAGS="-D__CHECK_ENDIAN__"
>
> However, this still doesn't enable endian checks. The correct syntax is:
>
> make C=2 CF="-D__CHECK_ENDIAN__"
>
> This documentation bug was introduced by the following commit:
>
> commit 1c7bafe7206d928eaccbcbd08d868733e0fb7054
> Author: Robert P. J. Day <rpjday@mindspring.com>
> Date: Wed Sep 13 07:57:50 2006 -0400
>
> kbuild: clarify "make C=" build option
>
> Clarify the use of "make C=" in the top-level Makefile, and fix a
> typo in the Documentation file.
>
> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
>
> This `typo' was not a typo, as `CF' had been introduced much earlier, by:
>
> commit 7b49bb9aff8b14d15da58111d8908c877c0a525e
> Author: viro@ZenIV.linux.org.uk <viro@ZenIV.linux.org.uk>
> Date: Fri Sep 9 21:14:35 2005 +0100
>
> [PATCH] kbuild: CF=<arguments> passes arguments to sparse
>
> Allows to add to sparse arguments without mutilating makefiles - just
> pass CF=<arguments> and they will be added to CHECKFLAGS.
>
> Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
> Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
>
> Signed-off-by: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Applied
Sam
prev parent reply other threads:[~2008-06-27 21:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 13:45 [PATCH] kbuild: sparse needs CF not CHECKFLAGS Geert Uytterhoeven
2008-06-27 21:07 ` Sam Ravnborg [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=20080627210727.GD29245@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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