From: Sam Ravnborg <sam@ravnborg.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, Zheng Liu <wenqing.lz@taobao.com>,
Christopher Li <sparse@chrisli.org>,
linux-sparse@vger.kernel.org
Subject: Re: [PATCH 03/10 v3] ext4: add physical block and status member into extent status tree
Date: Sun, 3 Feb 2013 08:30:13 +0100 [thread overview]
Message-ID: <20130203073013.GA25947@merkur.ravnborg.org> (raw)
In-Reply-To: <20130203030343.GB1359@thunk.org>
On Sat, Feb 02, 2013 at 10:03:43PM -0500, Theodore Ts'o wrote:
> On Wed, Jan 30, 2013 at 10:43:33AM +0800, Zheng Liu wrote:
> >
> > Clang is first coming in my mind. I know that some one try to use it
> > to build a linux kernel and get a lot of problems that are about gcc
> > extension. But for us it seems that things are not too bad. ;)
>
> Clang accepts bitfields with "unsigned long long", but I've discovered
> something which does _not_ support unsigned long long --- the "sparse"
> tool. :-(
>
> I discovered this when running "make C=1", i.e.:
>
> rm -f fs/ext4/extents_status.o
> make C=1 fs/ext4/extents_status.o
Small hint...
If you use:
make C=2 fs/ext4/extents_status.o
Then kbuild will run sparse on all targets you specify,
even if they do not need to be rebuild.
In other words - you then do not need to delete the .o file first.
This works for all the usual ways you can specify a target so to
check all of ext4 you just issue:
make C=2 fs/ext4/
Sam
prev parent reply other threads:[~2013-02-03 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1358942640-2262-1-git-send-email-wenqing.lz@taobao.com>
[not found] ` <1358942640-2262-4-git-send-email-wenqing.lz@taobao.com>
[not found] ` <20130129030353.GK7003@thunk.org>
[not found] ` <20130129053415.GA27002@gmail.com>
[not found] ` <20130129172814.GC4261@thunk.org>
[not found] ` <20130130024332.GA12111@gmail.com>
2013-02-03 3:03 ` [PATCH 03/10 v3] ext4: add physical block and status member into extent status tree Theodore Ts'o
2013-02-03 5:21 ` Zheng Liu
2013-02-03 8:19 ` Dan Carpenter
2013-02-03 14:57 ` Theodore Ts'o
2013-02-03 7:30 ` 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=20130203073013.GA25947@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
--cc=tytso@mit.edu \
--cc=wenqing.lz@taobao.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).