From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Song Liu <song@kernel.org>, Hannes Reinecke <hare@suse.de>,
Logan Gunthorpe <logang@deltatee.com>
Subject: [linux-next:master 11485/12552] drivers/md/md.c:8218:2-3: Unneeded semicolon
Date: Sat, 23 Jul 2022 04:58:57 +0800 [thread overview]
Message-ID: <202207230418.f7gno4mP-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 18c107a1f120d095404d141dfad8f594bdc44020
commit: d9406f31a96407754a05e1b6510b02684f622922 [11485/12552] md: only delete entries from all_mddevs when the disk is freed
config: alpha-randconfig-c032-20220721 (https://download.01.org/0day-ci/archive/20220723/202207230418.f7gno4mP-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 12.1.0
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
cocci warnings: (new ones prefixed by >>)
>> drivers/md/md.c:8218:2-3: Unneeded semicolon
--
0-DAY CI Kernel Test Service
https://01.org/lkp
reply other threads:[~2022-07-22 20:59 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=202207230418.f7gno4mP-lkp@intel.com \
--to=lkp@intel.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=logang@deltatee.com \
--cc=song@kernel.org \
/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