From: Fengguang Wu <fengguang.wu@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vyacheslav Dubeyko <slava@dubeyko.com>,
linux-fsdevel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Hin-Tak Leung <htl10@users.sourceforge.net>
Subject: Re: [PATCH] hfsplus: fix warnings in fs/hfsplus/bfind.c: In function 'hfs_find_1st_rec_by_cnid'
Date: Sat, 9 Mar 2013 08:28:36 +0800 [thread overview]
Message-ID: <20130309002836.GA8014@localhost> (raw)
In-Reply-To: <20130308142929.fd24d05b529d420fd7beaf1e@linux-foundation.org>
> I'm not particularly enthused about fixing CONFIG_BUG=n stuff. It's a
> nuisance.
Good to know that. I'll enforce CONFIG_BUG=y in the script.
That is, to run
scripts/config --file .config --enable CONFIG_BUG
after make randconfig/allnoconfig/...
Thanks,
Fengguang
prev parent reply other threads:[~2013-03-09 0:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 15:26 [PATCH] hfsplus: fix warnings in fs/hfsplus/bfind.c: In function 'hfs_find_1st_rec_by_cnid' Vyacheslav Dubeyko
2013-03-07 19:18 ` Andrew Morton
2013-03-08 13:15 ` Vyacheslav Dubeyko
2013-03-08 22:29 ` Andrew Morton
2013-03-09 0:28 ` Fengguang Wu [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=20130309002836.GA8014@localhost \
--to=fengguang.wu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=htl10@users.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=viro@zeniv.linux.org.uk \
/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).