Linux Documentation
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: "David Lechner (TI)" <dlechner@baylibre.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org
Subject: [dlech:b4/iio-adc-ti-ads122c14 1/14] htmldocs: Documentation/iio/ads112c14.rst:57: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Date: Sat, 01 Aug 2026 08:49:45 +0200	[thread overview]
Message-ID: <202608010857.ceqTcPRr-lkp@intel.com> (raw)

tree:   https://github.com/dlech/linux b4/iio-adc-ti-ads122c14
head:   c0c226e06d7019964f60738cde5a3eae4f0c0814
commit: 368fd704de0b90a9f9c30683d25db116ef8308bc [1/14] WIP
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/20260801/202608010857.ceqTcPRr-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/202608010857.ceqTcPRr-lkp@intel.com/

All warnings (new ones prefixed by >>):

   Runtime Survivability
   ===================== [docutils]
   Documentation/iio/ads112c14.rst:56: ERROR: Unexpected indentation. [docutils]
>> Documentation/iio/ads112c14.rst:57: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
   WARNING: ./include/linux/damon.h:909 struct member 'probes' not described in 'damon_ctx'
   WARNING: ./include/linux/damon.h:909 struct member 'rnd_state' not described in 'damon_ctx'
   WARNING: ./include/linux/damon.h:909 struct member 'probes' not described in 'damon_ctx'
   WARNING: ./include/linux/damon.h:909 struct member 'rnd_state' not described in 'damon_ctx'
   Documentation/mm/memfd_preservation:7: ./mm/memfd_luo.c:13: ERROR: Unexpected section title.
--
   Documentation/userspace-api/landlock:596: ./include/uapi/linux/landlock.h:63: ERROR: Unknown target name: "scope flags". [docutils]
   Documentation/userspace-api/landlock:596: ./include/uapi/linux/landlock.h:24: ERROR: Unknown target name: "filesystem flags". [docutils]
   Documentation/userspace-api/landlock:605: ./include/uapi/linux/landlock.h:228: ERROR: Unknown target name: "filesystem flags". [docutils]
   Documentation/userspace-api/landlock:605: ./include/uapi/linux/landlock.h:251: ERROR: Unknown target name: "network flags". [docutils]
   Documentation/networking/netlink_spec/index.rst: WARNING: document isn't included in any toctree [toc.not_included]
>> Documentation/iio/ads112c14.rst:22: WARNING: unknown document: '../devicetree/bindings/iio/adc/ti,ads112c14' [ref.doc]
   Documentation/networking/checksum-offloads:157: ./include/linux/skbuff.h:181: WARNING: Failed to create a cross reference. A title or caption not found: 'crc' [ref.ref]


vim +57 Documentation/iio/ads112c14.rst

    21	
  > 22	See :doc:`../devicetree/bindings/iio/adc/ti,ads112c14` for the complete
    23	binding description.
    24	
    25	The minimal device tree node looks like this::
    26	
    27	    adc@40 {
    28	        compatible = "ti,ads122c14";
    29	        reg = <0x40>;
    30	        avdd-supply = <&avdd>;
    31	        dvdd-supply = <&dvdd>;
    32	
    33	        /* TODO: add channel@ nodes here */
    34	    };
    35	
    36	Effect of devicetree on registers
    37	---------------------------------
    38	
    39	Device properties have the following effects on registers:
    40	
    41	* ``CLK_SEL`` and ``GPIO3_CFG`` are set if the ``clocks`` property is present.
    42	* ``GPIO2_SRC`` may be set when ``interrupts`` and ``interrupt-names`` for
    43	  "fault" is present.
    44	* ``GPIO3_SRC`` may be set when ``interrupts`` and ``interrupt-names`` for
    45	  "drdy" is present.
    46	
    47	Channel-specific properties have the following effects on registers only when
    48	a measurement is active on the channel:
    49	
    50	* ``AINP`` and ``AINN`` are set according to the ``single-channel`` or
    51	  ``diff-channel`` properties of each channel.
    52	* ``REF_SEL`` and ``REF_VAL`` will be set according to the value of the
    53	  ``reference-sources`` property.
    54	* When ``reference-sources`` is set to "external":
    55	  * If ``refp-supply`` is given and not the same phandle as ``avdd-supply``,
    56	    ``REFP_BUF_EN`` will be set to 1, otherwise it will be 0.
  > 57	  * If ``refn-supply`` is given, ``REFN_BUF_EN`` will be set to 1, otherwise it
    58	    will be 0.
    59	* ``I1MUX`` and ``I2MUX`` will be set to the values of the ``excitation-channels``
    60	   property.
    61	* ``IUNIT``, ``I1MAG`` and ``I2MAG`` will be set to best fit according to the
    62	   values of the ``excitation-current-nanoamp`` property.
    63	* ``GC_EN`` will be set to 1 if the ``input-chopping`` property is present,
    64	  otherwise it will be 0.
    65	* ``CODING`` is set based on the ``bipolar`` property.
    66	* ``DELAY`` is set based on the ``settling-time-us`` property.
    67	

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

                 reply	other threads:[~2026-08-01  6:50 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=202608010857.ceqTcPRr-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=dlechner@baylibre.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