All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android17-6.18-kminext 0/1] drivers/md/md-llbitmap.c:381:3-4: Unneeded semicolon
Date: Wed, 28 Oct 2026 06:08:53 +0100	[thread overview]
Message-ID: <202610280635.PHpkilv4-lkp@intel.com> (raw)

tree:   https://android.googlesource.com/kernel/common android17-6.18-kminext
head:   2cb883efa988e481f8a853178ec792f6fe49969e
commit: 5ab829f1971dc99f2aac10846c378e67fc875abc [0/1] md/md-llbitmap: introduce new lockless bitmap
config: i386-randconfig-2102-20261028 (https://download.01.org/0day-ci/archive/20261028/202610280635.PHpkilv4-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0

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
| Fixes: 5ab829f1971d ("md/md-llbitmap: introduce new lockless bitmap")
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202610280635.PHpkilv4-lkp@intel.com/

cocci warnings: (new ones prefixed by >>)
>> drivers/md/md-llbitmap.c:381:3-4: Unneeded semicolon

vim +381 drivers/md/md-llbitmap.c

   363	
   364	/* set all the bits in the subpage as dirty */
   365	static void llbitmap_infect_dirty_bits(struct llbitmap *llbitmap,
   366					       struct llbitmap_page_ctl *pctl,
   367					       unsigned int block)
   368	{
   369		bool level_456 = raid_is_456(llbitmap->mddev);
   370		unsigned int io_size = llbitmap->io_size;
   371		int pos;
   372	
   373		for (pos = block * io_size; pos < (block + 1) * io_size; pos++) {
   374			switch (pctl->state[pos]) {
   375			case BitUnwritten:
   376				pctl->state[pos] = level_456 ? BitNeedSync : BitDirty;
   377				break;
   378			case BitClean:
   379				pctl->state[pos] = BitDirty;
   380				break;
 > 381			};
   382		}
   383	}
   384	

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

                 reply	other threads:[~2026-10-28  5:09 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=202610280635.PHpkilv4-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --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.