From: kernel test robot <lkp@intel.com>
To: Keith Busch <kbusch@meta.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCHv6 6/8] blk-mq-dma: add support for mapping integrity metadata
Date: Wed, 13 Aug 2025 13:28:16 +0800 [thread overview]
Message-ID: <202508131303.nL4SARD7-lkp@intel.com> (raw)
In-Reply-To: <20250812135210.4172178-7-kbusch@meta.com>
Hi Keith,
kernel test robot noticed the following build warnings:
[auto build test WARNING on axboe-block/for-next]
[also build test WARNING on linus/master v6.17-rc1 next-20250812]
[cannot apply to linux-nvme/for-next]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Keith-Busch/blk-mq-dma-create-blk_map_iter-type/20250812-222130
base: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git for-next
patch link: https://lore.kernel.org/r/20250812135210.4172178-7-kbusch%40meta.com
patch subject: [PATCHv6 6/8] blk-mq-dma: add support for mapping integrity metadata
config: csky-randconfig-001-20250813 (https://download.01.org/0day-ci/archive/20250813/202508131303.nL4SARD7-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 14.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250813/202508131303.nL4SARD7-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/202508131303.nL4SARD7-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> block/blk-mq-dma.c:10:13: warning: '__blk_map_iter_next' defined but not used [-Wunused-function]
10 | static bool __blk_map_iter_next(struct blk_map_iter *iter)
| ^~~~~~~~~~~~~~~~~~~
vim +/__blk_map_iter_next +10 block/blk-mq-dma.c
9
> 10 static bool __blk_map_iter_next(struct blk_map_iter *iter)
11 {
12 if (iter->iter.bi_size)
13 return true;
14 if (!iter->bio || !iter->bio->bi_next)
15 return false;
16
17 iter->bio = iter->bio->bi_next;
18 if (iter->is_integrity) {
19 iter->iter = bio_integrity(iter->bio)->bip_iter;
20 iter->bvecs = bio_integrity(iter->bio)->bip_vec;
21 } else {
22 iter->iter = iter->bio->bi_iter;
23 iter->bvecs = iter->bio->bi_io_vec;
24 }
25 return true;
26 }
27
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-13 5:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 13:52 [PATCHv6 0/8] blk dma iter for integrity metadata Keith Busch
2025-08-12 13:52 ` [PATCHv6 1/8] blk-mq-dma: create blk_map_iter type Keith Busch
2025-08-12 16:24 ` Christoph Hellwig
2025-08-12 13:52 ` [PATCHv6 2/8] blk-mq-dma: provide the bio_vec array being iterated Keith Busch
2025-08-12 16:24 ` Christoph Hellwig
2025-08-12 13:52 ` [PATCHv6 3/8] blk-mq-dma: require unmap caller provide p2p map type Keith Busch
2025-08-12 13:52 ` [PATCHv6 4/8] blk-mq: remove REQ_P2PDMA flag Keith Busch
2025-08-12 13:52 ` [PATCHv6 5/8] blk-mq-dma: move common dma start code to a helper Keith Busch
2025-08-12 13:52 ` [PATCHv6 6/8] blk-mq-dma: add support for mapping integrity metadata Keith Busch
2025-08-13 5:28 ` kernel test robot [this message]
2025-08-13 6:50 ` Christoph Hellwig
2025-08-12 13:52 ` [PATCHv6 7/8] nvme-pci: create common sgl unmapping helper Keith Busch
2025-08-13 6:51 ` Christoph Hellwig
2025-08-12 13:52 ` [PATCHv6 8/8] nvme-pci: convert metadata mapping to dma iter Keith Busch
2025-08-13 6:52 ` Christoph Hellwig
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=202508131303.nL4SARD7-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbusch@meta.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.