From: kernel test robot <lkp@intel.com>
To: Rodrigo Alencar <rodrigo.alencar@analog.com>
Cc: oe-kbuild-all@lists.linux.dev, 0day robot <lkp@intel.com>,
linux-doc@vger.kernel.org
Subject: htmldocs: Documentation/iio/ad9910.rst:451: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Date: Sun, 19 Apr 2026 14:24:54 +0200 [thread overview]
Message-ID: <202604191436.eNqraDV2-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/Rodrigo-Alencar-via-B4-Relay/dt-bindings-iio-frequency-add-ad9910/20260419-104913
head: 5ac9bfbe149f0815ff3156530d694c8c4a39dc75
commit: 5ac9bfbe149f0815ff3156530d694c8c4a39dc75 docs: iio: add documentation for ad9910 driver
date: 9 hours ago
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
docutils: docutils (Docutils 0.21.2, Python 3.13.5, on linux)
reproduce: (https://download.01.org/0day-ci/archive/20260419/202604191436.eNqraDV2-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/202604191436.eNqraDV2-lkp@intel.com/
All warnings (new ones prefixed by >>):
Runtime Survivability
===================== [docutils]
Documentation/iio/ad9910.rst:444: ERROR: Unexpected indentation. [docutils]
Documentation/iio/ad9910.rst:447: ERROR: Unexpected indentation. [docutils]
>> Documentation/iio/ad9910.rst:451: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/iio/ad9910.rst:452: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]
Documentation/iio/ad9910.rst:459: ERROR: Unexpected indentation. [docutils]
Documentation/mm/memfd_preservation:7: ./mm/memfd_luo.c:13: ERROR: Unexpected section title.
vim +451 Documentation/iio/ad9910.rst
440
441 - 72-byte header:
442 - 4-byte big-endian word count: number of 32-bit words to be loaded (0-1024)
443 - 4-byte big-endian CFR1 value: configuration for the CFR1 register. Only
444 bits relevant to RAM mode (data destination and internal profile control)
445 are considered. Other bits are ignored and have no effect.
446 - Bits [30:29]: RAM data destination:
447 - 00: frequency
448 - 01: phase
449 - 10: amplitude
450 - 11: polar
> 451 - Bits [20:17]: Internal profile control (see Table 14 of the datasheet).
452 - 8 sets of 8-byte big-endian profile data for profiles 0-7. Each set contains:
453 - Bits [55:40]: Address step rate value
454 - Bits [39:30]: End address for the profile
455 - Bits [23:14]: Start address for the profile
456 - Bit [5]: no-dwell high for ramp-up mode
457 - Bit [3]: zero-crossing for direct-switch mode
458 - Bits [2:0]: operating mode:
459 - 000: direct switch
460 - 001: ramp-up
461 - 010: bidirectional
462 - 011: bidirectional continuous
463 - 100: ramp-up continuous
464 - Followed by the specified number of 32-bit big-endian data words.
465
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-04-19 12:25 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=202604191436.eNqraDV2-lkp@intel.com \
--to=lkp@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rodrigo.alencar@analog.com \
/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