mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
	"kbuild test robot" <lkp@intel.com>
Cc: <kbuild-all@01.org>, <linux-f2fs-devel@lists.sourceforge.net>,
	<jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
	<stable@vger.kernel.org>
Subject: Re: [PATCH 1/1] f2fs: fix validation of the block count in sanity_check_raw_super
Date: Mon, 24 Dec 2018 16:18:25 +0800	[thread overview]
Message-ID: <0ad23150-72df-4bcc-851e-1da306e5a027@huawei.com> (raw)
In-Reply-To: <CAFBinCA=-st_bM0Cz7mu-Hq6Asv5HAXPMwDZUjMj6GqMb8s=hw@mail.gmail.com>

On 2018/12/22 19:08, Martin Blumenstingl wrote:
> On Sat, Dec 22, 2018 at 8:00 AM kbuild test robot <lkp@intel.com> wrote:
>>
>> Hi Martin,
>>
>> Thank you for the patch! Perhaps something to improve:
>>
>> [auto build test WARNING on f2fs/dev-test]
>> [also build test WARNING on v4.20-rc7 next-20181221]
>> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
>>
>> url:    https://github.com/0day-ci/linux/commits/Martin-Blumenstingl/f2fs-fix-sanity_check_raw_super-on-big-endian-machines/20181222-142616
>> base:   https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
>> config: i386-randconfig-x006-201850 (attached as .config)
>> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
>> reproduce:
>>         # save the attached .config to linux build tree
>>         make ARCH=i386
>>
>> All warnings (new ones prefixed by >>):
>>
>>    fs/f2fs/super.c: In function 'sanity_check_raw_super':
>>>> fs/f2fs/super.c:2498:46: warning: format '%u' expects argument of type 'unsigned int', but argument 5 has type 'long long unsigned int' [-Wformat=]
>>        "Wrong segment_count / block_count (%u > %u)",
>>                                                 ~^
>>                                                 %llu
> I sent a v2 with this fixed and Chao Yu's reviewed by included

Sorry, I didn't catch previous print issue on v1, anyway, I'm okay with v2. :)

Thanks,

> 
> .
> 


  reply	other threads:[~2018-12-24  8:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21 19:28 [PATCH 0/1] f2fs: fix sanity_check_raw_super on big endian machines Martin Blumenstingl
2018-12-21 19:28 ` [PATCH 1/1] f2fs: fix validation of the block count in sanity_check_raw_super Martin Blumenstingl
2018-12-22  2:24   ` Chao Yu
2018-12-22  7:00   ` kbuild test robot
2018-12-22 11:08     ` Martin Blumenstingl
2018-12-24  8:18       ` Chao Yu [this message]
2018-12-22  9:30   ` kbuild test robot

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=0ad23150-72df-4bcc-851e-1da306e5a027@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=jaegeuk@kernel.org \
    --cc=kbuild-all@01.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=stable@vger.kernel.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

all inboxes | Powered by JetHome®