From: kernel test robot <lkp@intel.com>
To: Jiri Pirko <jiri@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org
Subject: [jpirko-mlxsw:wip_attestation_pre_rfc_draft1 9/26] htmldocs: Documentation/driver-api/ctlv.rst:652: WARNING: Explicit markup ends without a blank line; unexpected unindent. [docutils]
Date: Wed, 30 Sep 2026 05:44:01 +0200 [thread overview]
Message-ID: <202609300542.1d5tRFLl-lkp@intel.com> (raw)
tree: https://github.com/jpirko/linux_mlxsw wip_attestation_pre_rfc_draft1
head: a18af4e1b514bf11f88ca42d29b7b68f3b375378
commit: d4c78d56bb6c57a152d81d5d8442f520863f503e [9/26] Documentation: ctlv: Describe how to write a family
compiler: clang version 22.1.8 (https://github.com/llvm/llvm-project ca7933e47d3a3451d81e72ac174dcb5aa28b59d1)
docutils: docutils (Docutils 0.21.2, Python 3.13.5, on linux)
reproduce: (https://download.01.org/0day-ci/archive/20260930/202609300542.1d5tRFLl-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/202609300542.1d5tRFLl-lkp@intel.com/
All warnings (new ones prefixed by >>):
WARNING: ./block/blk-map.c:366 Excess function parameter 'op' description in 'bio_copy_kern'
Documentation/driver-api/basics:42: ./kernel/time/time.c:370: WARNING: Duplicate C declaration, also defined at driver-api/basics:436.
Declaration is '.. c:function:: unsigned int jiffies_to_msecs (const unsigned long j)'. [duplicate_declaration.c]
Documentation/driver-api/basics:42: ./kernel/time/time.c:393: WARNING: Duplicate C declaration, also defined at driver-api/basics:453.
Declaration is '.. c:function:: unsigned int jiffies_to_usecs (const unsigned long j)'. [duplicate_declaration.c]
>> Documentation/driver-api/ctlv.rst:652: WARNING: Explicit markup ends without a blank line; unexpected unindent. [docutils]
Documentation/driver-api/ctlv.rst:655: ERROR: Unexpected indentation. [docutils]
>> Documentation/driver-api/ctlv.rst:661: WARNING: Definition list ends without a blank line; unexpected unindent. [docutils]
WARNING: ./include/linux/device.h:117 struct member 'show_const' not described in 'device_attribute'
WARNING: ./include/linux/device.h:117 struct member 'store_const' not described in 'device_attribute'
WARNING: ./include/linux/dma-fence-array.h:47 Excess struct member 'lock' description in 'dma_fence_array'
WARNING: ./include/linux/dma-fence-array.h:47 Excess struct member 'lock' description in 'dma_fence_array'
WARNING: ./include/linux/dma-fence-chain.h:48 Excess struct member 'lock' description in 'dma_fence_chain'
vim +652 Documentation/driver-api/ctlv.rst
630
631 struct ctlv_blob_dma *dma;
632 struct dma_fence *fence;
633 struct sg_table *sgt;
634 u64 skip;
635
636 dma = ctlv_blob_dma_map(blob, dev, &sgt, &skip);
637 if (IS_ERR(dma)) {
638 ret = PTR_ERR(dma);
639 goto out_blob;
640 }
641 fence = prepare_job(sgt, skip, ctlv_blob_len(blob));
642 if (IS_ERR(fence)) {
643 ret = PTR_ERR(fence);
644 goto out_dma;
645 }
646 ret = ctlv_blob_dma_begin(dma, fence);
647 if (!ret) {
648 ret = submit_prepared_job(fence);
649 ctlv_blob_dma_submit_done(dma, ret);
650 }
651 /* On success, the completion path signals fence after hardware stops. */
> 652 out_dma:
653 ctlv_blob_dma_unmap(dma, ret);
654 if (!IS_ERR(fence))
655 dma_fence_put(fence);
656 out_blob:
657 if (!ret)
658 ret = ctlv_blob_put(blob);
659 else
660 ctlv_blob_put(blob);
> 661 return ret;
662
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-09-30 3:44 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=202609300542.1d5tRFLl-lkp@intel.com \
--to=lkp@intel.com \
--cc=jiri@nvidia.com \
--cc=linux-doc@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox