Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
	Chao Yu <yuchao0@huawei.com>, Chao Yu <chao@kernel.org>
Subject: [chao:bugfix/common 3/9] fs/f2fs/f2fs.h:2100:50: error: passing 'const struct folio *' to parameter of type 'struct folio *' discards qualifiers
Date: Fri, 9 May 2025 03:10:02 +0800	[thread overview]
Message-ID: <202505090256.TMKDR2XH-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git bugfix/common
head:   2860d2a634860b83a27a71e5db3c2c416a59008a
commit: a14b19bd94199c525031bdc63821ab086f4c70bf [3/9] f2fs: introduce is_{meta,node}_folio
config: s390-allmodconfig (https://download.01.org/0day-ci/archive/20250509/202505090256.TMKDR2XH-lkp@intel.com/config)
compiler: clang version 18.1.8 (https://github.com/llvm/llvm-project 3b5b5c1ec4a3095ab096dd780e84d7ab81f3d7ff)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250509/202505090256.TMKDR2XH-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/202505090256.TMKDR2XH-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from fs/f2fs/dir.c:13:
>> fs/f2fs/f2fs.h:2100:50: error: passing 'const struct folio *' to parameter of type 'struct folio *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
    2100 |         return folio->mapping == META_MAPPING(F2FS_F_SB(folio));
         |                                                         ^~~~~
   fs/f2fs/f2fs.h:2023:60: note: passing argument to parameter 'folio' here
    2023 | static inline struct f2fs_sb_info *F2FS_F_SB(struct folio *folio)
         |                                                            ^
   fs/f2fs/f2fs.h:2105:50: error: passing 'const struct folio *' to parameter of type 'struct folio *' discards qualifiers [-Werror,-Wincompatible-pointer-types-discards-qualifiers]
    2105 |         return folio->mapping == NODE_MAPPING(F2FS_F_SB(folio));
         |                                                         ^~~~~
   fs/f2fs/f2fs.h:2023:60: note: passing argument to parameter 'folio' here
    2023 | static inline struct f2fs_sb_info *F2FS_F_SB(struct folio *folio)
         |                                                            ^
   2 errors generated.


vim +2100 fs/f2fs/f2fs.h

  2097	
  2098	static inline bool is_meta_folio(const struct folio *folio)
  2099	{
> 2100		return folio->mapping == META_MAPPING(F2FS_F_SB(folio));
  2101	}
  2102	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

                 reply	other threads:[~2025-05-08 19:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=202505090256.TMKDR2XH-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=chao@kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=yuchao0@huawei.com \
    /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