All of lore.kernel.org
 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:wip 1/5] fs/f2fs/f2fs.h:4902:43: error: no member named 'first_zoned_segno' in 'struct f2fs_sb_info'; did you mean 'first_seq_zone_segno'?
Date: Sat, 31 May 2025 13:59:42 +0800	[thread overview]
Message-ID: <202505311327.eFLLIgds-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/chao/linux.git wip
head:   da08611e28ee951df3ed7bfa4d0d8174ed763ebf
commit: d6f1da168279ee76658fa5907d6cbaf30447717e [1/5] f2fs: zone: allow IPU for regular file in regular block device
config: s390-randconfig-002-20250531 (https://download.01.org/0day-ci/archive/20250531/202505311327.eFLLIgds-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project f819f46284f2a79790038e1f6649172789734ae8)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250531/202505311327.eFLLIgds-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/202505311327.eFLLIgds-lkp@intel.com/

All errors (new ones prefixed by >>):

   In file included from fs/f2fs/extent_cache.c:18:
>> fs/f2fs/f2fs.h:4902:43: error: no member named 'first_zoned_segno' in 'struct f2fs_sb_info'; did you mean 'first_seq_zone_segno'?
    4902 |         return f2fs_sb_has_blkzoned(sbi) && sbi->first_zoned_segno;
         |                                                  ^~~~~~~~~~~~~~~~~
         |                                                  first_seq_zone_segno
   fs/f2fs/f2fs.h:1796:15: note: 'first_seq_zone_segno' declared here
    1796 |         unsigned int first_seq_zone_segno;      /* first segno in sequential zone */
         |                      ^
   1 error generated.
--
   In file included from fs/f2fs/data.c:24:
>> fs/f2fs/f2fs.h:4902:43: error: no member named 'first_zoned_segno' in 'struct f2fs_sb_info'; did you mean 'first_seq_zone_segno'?
    4902 |         return f2fs_sb_has_blkzoned(sbi) && sbi->first_zoned_segno;
         |                                                  ^~~~~~~~~~~~~~~~~
         |                                                  first_seq_zone_segno
   fs/f2fs/f2fs.h:1796:15: note: 'first_seq_zone_segno' declared here
    1796 |         unsigned int first_seq_zone_segno;      /* first segno in sequential zone */
         |                      ^
>> fs/f2fs/data.c:2609:11: error: no member named 'first_zoned_segno' in 'struct f2fs_sb_info'; did you mean 'first_seq_zone_segno'?
    2609 |                                         sbi->first_zoned_segno)
         |                                              ^~~~~~~~~~~~~~~~~
         |                                              first_seq_zone_segno
   fs/f2fs/f2fs.h:1796:15: note: 'first_seq_zone_segno' declared here
    1796 |         unsigned int first_seq_zone_segno;      /* first segno in sequential zone */
         |                      ^
   2 errors generated.


vim +4902 fs/f2fs/f2fs.h

  4899	
  4900	static inline bool f2fs_blkzoned_has_regular_section(struct f2fs_sb_info *sbi)
  4901	{
> 4902		return f2fs_sb_has_blkzoned(sbi) && sbi->first_zoned_segno;
  4903	}
  4904	

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

                 reply	other threads:[~2025-05-31  6:00 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=202505311327.eFLLIgds-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.