Hi Jakub, kernel test robot noticed the following build warnings:
[auto build test WARNING on net-next/main] url: https://github.com/intel-lab-lkp/linux/commits/Jakub-Kicinski/docs-exclude-driver-and-netdevsim-bugs/20260604-003949 base: net-next/main patch link: https://lore.kernel.org/r/20260603162943.2406080-1-kuba%40kernel.org patch subject: [PATCH net-next] docs: exclude driver and netdevsim bugs compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project f43d6834093b19baf79beda8c0337ab020ac5f17) docutils: docutils (Docutils 0.21.2, Python 3.13.5, on linux) reproduce: (https://download.01.org/0day-ci/archive/20260604/[email protected]/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 <[email protected]> | Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/ All warnings (new ones prefixed by >>): Checksumming on output with GSO ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [docutils] Documentation/process/maintainer-netdev.rst:295: ERROR: Unexpected indentation. [docutils] >> Documentation/process/maintainer-netdev.rst:299: WARNING: Block quote ends >> without a blank line; unexpected unindent. [docutils] MAINTAINERS:40: WARNING: Inline strong start-string without end-string. [docutils] Documentation/userspace-api/landlock:504: ./security/landlock/errata/abi-4.h:5: ERROR: Unexpected section title. vim +299 Documentation/process/maintainer-netdev.rst 292 293 Additionally, netdev does not consider bugs to be ``net``-worthy 294 if they fulfill **all** of the following criteria: 295 - bug is in a hardware device driver; 296 - bug is either a missing error handling or is part of the error handling flow; 297 - bug was discovered by a static analysis / AI tool; 298 - bug was triggered/observed only with kernel changes or fault injection. > 299 Fixes for such bugs should default to ``net-next`` and should **not** > contain 300 a Fixes tag. Networking or driver maintainers may redirect such fixes to ``net`` 301 at their discretion if they consider the condition to be relevant enough. 302 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki
