From: kbuild test robot <lkp@intel.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: kbuild-all@01.org,
Ext4 Developers List <linux-ext4@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
stable@kernel.org
Subject: Re: [PATCH] ext4: add ext4_sb_bread() to disambiguate ENOMEM cases
Date: Tue, 20 Nov 2018 21:36:39 +0800 [thread overview]
Message-ID: <201811202145.0H2GYODQ%fengguang.wu@intel.com> (raw)
In-Reply-To: <20181117233523.8832-1-tytso@mit.edu>
Hi Theodore,
I love your patch! Perhaps something to improve:
[auto build test WARNING on ext4/dev]
[also build test WARNING on v4.20-rc3 next-20181120]
[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/Theodore-Ts-o/ext4-add-ext4_sb_bread-to-disambiguate-ENOMEM-cases/20181120-070629
base: https://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
coccinelle warnings: (new ones prefixed by >>)
>> fs/ext4/resize.c:1000:9-16: ERROR: PTR_ERR applied after initialization to constant on line 989
--
>> fs/ext4/resize.c:999:6-12: inconsistent IS_ERR and PTR_ERR on line 1000.
Please review and possibly fold the followup patch.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
next prev parent reply other threads:[~2018-11-21 0:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-17 23:35 [PATCH] ext4: add ext4_sb_bread() to disambiguate ENOMEM cases Theodore Ts'o
2018-11-20 1:14 ` kbuild test robot
2018-11-20 13:36 ` kbuild test robot [this message]
2018-11-20 13:36 ` [PATCH] ext4: fix odd_ptr_err.cocci warnings kbuild test robot
2018-11-22 12:21 ` [PATCH] ext4: add ext4_sb_bread() to disambiguate ENOMEM cases Jan Kara
2018-11-22 21:12 ` Theodore Y. Ts'o
2018-11-22 22:18 ` [PATCH -v2] " Theodore Ts'o
2018-11-23 12:15 ` [PATCH] " Jan Kara
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=201811202145.0H2GYODQ%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-ext4@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tytso@mit.edu \
/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).