From: kernel test robot <lkp@intel.com>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [koverstreet-bcachefs:trace_sched_wakeup_backtrace 21/332] fs/bcachefs/btree/interior.h:136:18: sparse: sparse: mixing different enum types:
Date: Sat, 16 May 2026 05:50:27 +0800 [thread overview]
Message-ID: <202605160556.5fW4SjGm-lkp@intel.com> (raw)
tree: https://github.com/koverstreet/bcachefs trace_sched_wakeup_backtrace
head: 9e7cbd4ad9c7a7ba461dbba9185628c006e200cd
commit: ef4225fd3371dd0ce8b31150446324c3bd268589 [21/332] bcachefs: Btree node rewrites don't run at BCH_WATERMARK_btree
config: sh-randconfig-r123-20260514 (https://download.01.org/0day-ci/archive/20260516/202605160556.5fW4SjGm-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 11.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260516/202605160556.5fW4SjGm-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/202605160556.5fW4SjGm-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
fs/bcachefs/data/move.c: note: in included file:
>> fs/bcachefs/btree/interior.h:136:18: sparse: sparse: mixing different enum types:
fs/bcachefs/btree/interior.h:136:18: sparse: unsigned int enum bch_trans_commit_flags
fs/bcachefs/btree/interior.h:136:18: sparse: unsigned int enum bch_watermark
--
fs/bcachefs/btree/interior.c: note: in included file:
>> fs/bcachefs/btree/interior.h:136:18: sparse: sparse: mixing different enum types:
fs/bcachefs/btree/interior.h:136:18: sparse: unsigned int enum bch_trans_commit_flags
fs/bcachefs/btree/interior.h:136:18: sparse: unsigned int enum bch_watermark
>> fs/bcachefs/btree/interior.h:136:18: sparse: sparse: mixing different enum types:
fs/bcachefs/btree/interior.h:136:18: sparse: unsigned int enum bch_trans_commit_flags
fs/bcachefs/btree/interior.h:136:18: sparse: unsigned int enum bch_watermark
vim +136 fs/bcachefs/btree/interior.h
125
126 static inline enum bch_trans_commit_flags
127 btree_update_set_watermark_hipri(enum bch_trans_commit_flags flags)
128 {
129 enum bch_watermark watermark = flags & BCH_WATERMARK_MASK;
130 if (watermark == BCH_WATERMARK_copygc)
131 watermark = BCH_WATERMARK_btree_copygc;
132 if (watermark < BCH_WATERMARK_btree)
133 watermark = BCH_WATERMARK_btree;
134
135 flags &= ~BCH_WATERMARK_MASK;
> 136 flags |= watermark;
137 return flags;
138 }
139
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-05-15 21:50 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=202605160556.5fW4SjGm-lkp@intel.com \
--to=lkp@intel.com \
--cc=kent.overstreet@linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
/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.