From: kernel test robot <lkp@intel.com>
To: dslab@lzu.edu.cn, jaegeuk@kernel.org, chao@kernel.org
Cc: Yang Hubin <yanghb2019@lzu.edu.cn>,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev,
linux-f2fs-devel@lists.sourceforge.net,
oe-kbuild-all@lists.linux.dev
Subject: Re: [f2fs-dev] [PATCH] f2fs: the name of a struct is wrong in a comment.
Date: Wed, 8 Nov 2023 03:18:36 +0800 [thread overview]
Message-ID: <202311080247.0hkA0mLH-lkp@intel.com> (raw)
In-Reply-To: <20231106121418.3675-1-dslab@lzu.edu.cn>
Hi,
kernel test robot noticed the following build errors:
[auto build test ERROR on jaegeuk-f2fs/dev-test]
[also build test ERROR on jaegeuk-f2fs/dev linus/master v6.6 next-20231107]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/dslab-lzu-edu-cn/f2fs-the-name-of-a-struct-is-wrong-in-a-comment/20231106-201822
base: https://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git dev-test
patch link: https://lore.kernel.org/r/20231106121418.3675-1-dslab%40lzu.edu.cn
patch subject: [PATCH] f2fs: the name of a struct is wrong in a comment.
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20231108/202311080247.0hkA0mLH-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231108/202311080247.0hkA0mLH-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202311080247.0hkA0mLH-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from fs/f2fs/dir.c:10:
>> include/linux/f2fs_fs.h:501:16: error: expected ']'
__u8 reserved[NAT_JOURNAL_RESERVED];
^
include/linux/f2fs_fs.h:474:38: note: expanded from macro 'NAT_JOURNAL_RESERVED'
sizeof(struct nat_journal_entry))SIT_JOURNA
^
include/linux/f2fs_fs.h:501:15: note: to match this '['
__u8 reserved[NAT_JOURNAL_RESERVED];
^
1 error generated.
vim +501 include/linux/f2fs_fs.h
dd31866b0d55c9 Jaegeuk Kim 2012-11-02 498
dd31866b0d55c9 Jaegeuk Kim 2012-11-02 499 struct nat_journal {
dd31866b0d55c9 Jaegeuk Kim 2012-11-02 500 struct nat_journal_entry entries[NAT_JOURNAL_ENTRIES];
dd31866b0d55c9 Jaegeuk Kim 2012-11-02 @501 __u8 reserved[NAT_JOURNAL_RESERVED];
dd31866b0d55c9 Jaegeuk Kim 2012-11-02 502 } __packed;
dd31866b0d55c9 Jaegeuk Kim 2012-11-02 503
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2023-11-07 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231106121418.3675-1-dslab@lzu.edu.cn>
2023-11-07 6:42 ` [f2fs-dev] [PATCH] f2fs: the name of a struct is wrong in a comment kernel test robot
2023-11-07 19:18 ` kernel test robot [this message]
[not found] <20231104074501.13998-1-dslab@lzu.edu.cn>
2023-11-07 14:56 ` Chao Yu
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=202311080247.0hkA0mLH-lkp@intel.com \
--to=lkp@intel.com \
--cc=chao@kernel.org \
--cc=dslab@lzu.edu.cn \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=yanghb2019@lzu.edu.cn \
/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).