From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android16-6.12-2025-09 0/1] htmldocs: ./block/blk-core.c:894: warning: duplicate section name 'Note'
Date: Thu, 18 Sep 2025 11:24:15 +0200 [thread overview]
Message-ID: <202509181101.qaRdFPsS-lkp@intel.com> (raw)
Hi Bart,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android16-6.12-2025-09
head: 3eff75f14ff67c968fa98c407cb55532722b6655
commit: d6f0f66569f2f74c9095a8c4e8c43bff2b571769 [0/1] ANDROID: block: Do not set the I/O priority for zoned writes
reproduce: (https://download.01.org/0day-ci/archive/20250918/202509181101.qaRdFPsS-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/202509181101.qaRdFPsS-lkp@intel.com/
All warnings (new ones prefixed by >>):
Error: Cannot open file ./include/linux/math64.h
Error: Cannot open file ./include/linux/math64.h
Error: Cannot open file ./include/linux/kfifo.h
Error: Cannot open file ./include/linux/kfifo.h
Error: Cannot open file ./include/linux/bio.h
>> ./block/blk-core.c:894: warning: duplicate section name 'Note'
>> ./block/blk-core.c:894: warning: duplicate section name 'Note'
Error: Cannot open file ./include/linux/clk.h
Error: Cannot open file ./include/linux/clk.h
Error: Cannot open file ./include/linux/rcupdate.h
Error: Cannot open file ./include/linux/srcu.h
Error: Cannot open file ./include/linux/rculist_bl.h
vim +/Note +894 ./block/blk-core.c
884
885 #ifdef CONFIG_BLK_DEV_ZONED
886 /**
887 * blk_bio_is_seq_zoned_write() - Check if @bio requires write serialization.
888 * @bio: Bio to examine.
889 *
890 * Note: REQ_OP_ZONE_APPEND bios do not require serialization.
891 * Note: this function treats conventional zones on a zoned block device as
892 * sequential zones. This is fine since zoned UFS devices have no conventional
893 * zones.
> 894 */
895 static bool blk_bio_is_seq_zoned_write(struct bio *bio)
896 {
897 if (!bdev_is_zoned(bio->bi_bdev))
898 return false;
899
900 return bio_op(bio) == REQ_OP_WRITE ||
901 bio_op(bio) == REQ_OP_WRITE_ZEROES;
902 }
903 #else
904 static bool blk_bio_is_seq_zoned_write(struct bio *bio)
905 {
906 return false;
907 }
908 #endif
909
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-09-18 9:24 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=202509181101.qaRdFPsS-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.