From: kernel test robot <lkp@intel.com>
To: Chengguang Xu <cgxu519@mykernel.net>, jack@suse.com
Cc: kbuild-all@lists.01.org, linux-ext4@vger.kernel.org,
Chengguang Xu <cgxu519@mykernel.net>
Subject: Re: [PATCH] ext2: implement ->page_mkwrite
Date: Sun, 27 Dec 2020 07:54:01 +0800 [thread overview]
Message-ID: <202012270705.V7iFS8YJ-lkp@intel.com> (raw)
In-Reply-To: <20201218132757.279685-1-cgxu519@mykernel.net>
[-- Attachment #1: Type: text/plain, Size: 1755 bytes --]
Hi Chengguang,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v5.10 next-20201223]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Chengguang-Xu/ext2-implement-page_mkwrite/20201218-214646
base: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git a409ed156a90093a03fe6a93721ddf4c591eac87
config: i386-randconfig-s002-20201217 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce:
# apt-get install sparse
# sparse version: v0.6.3-184-g1b896707-dirty
# https://github.com/0day-ci/linux/commit/24259119fbeffce3b221c39c3b8bc0f2d5b1e750
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Chengguang-Xu/ext2-implement-page_mkwrite/20201218-214646
git checkout 24259119fbeffce3b221c39c3b8bc0f2d5b1e750
# save the attached .config to linux build tree
make W=1 C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=i386
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
"sparse warnings: (new ones prefixed by >>)"
>> fs/ext2/file.c:33:12: sparse: sparse: symbol 'ext2_page_mkwrite' was not declared. Should it be static?
>> fs/ext2/file.c:50:35: sparse: sparse: symbol 'ext2_vm_ops' was not declared. Should it be static?
Please review and possibly fold the followup patch.
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 37959 bytes --]
next prev parent reply other threads:[~2020-12-26 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 13:27 [PATCH] ext2: implement ->page_mkwrite Chengguang Xu
2020-12-19 23:32 ` kernel test robot
2020-12-26 23:54 ` kernel test robot [this message]
2020-12-26 23:54 ` [RFC PATCH] ext2: ext2_page_mkwrite() can be static kernel test robot
2021-01-05 17:53 ` [PATCH] ext2: implement ->page_mkwrite 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=202012270705.V7iFS8YJ-lkp@intel.com \
--to=lkp@intel.com \
--cc=cgxu519@mykernel.net \
--cc=jack@suse.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).