From: kernel test robot <lkp@intel.com>
To: Diogo Pimenta <diogo2003pimenta@gmail.com>,
broonie@kernel.org, linux-spi@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Diogo Pimenta <diogo2003.pimenta@gmail.com>
Subject: Re: [PATCH] Documentation: spi: add SPDX license identifier
Date: Thu, 11 Jun 2026 10:51:28 +0200 [thread overview]
Message-ID: <202606111027.TFnhhj2n-lkp@intel.com> (raw)
In-Reply-To: <20260611003242.44820-1-diogo2003.pimenta@gmail.com>
Hi Diogo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on broonie-spi/for-next]
[also build test WARNING on linus/master v7.1-rc7 next-20260610]
[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/Diogo-Pimenta/Documentation-spi-add-SPDX-license-identifier/20260611-083409
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
patch link: https://lore.kernel.org/r/20260611003242.44820-1-diogo2003.pimenta%40gmail.com
patch subject: [PATCH] Documentation: spi: add SPDX license identifier
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/20260611/202606111027.TFnhhj2n-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/202606111027.TFnhhj2n-lkp@intel.com/
All warnings (new ones prefixed by >>):
Checksumming on output with GSO
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [docutils]
MAINTAINERS:40: WARNING: Inline strong start-string without end-string. [docutils]
>> Documentation/spi/spi-summary.rst:2: WARNING: Explicit markup ends without a blank line; unexpected unindent. [docutils]
Documentation/userspace-api/landlock:504: ./security/landlock/errata/abi-4.h:5: ERROR: Unexpected section title.
vim +2 Documentation/spi/spi-summary.rst
9cdd273e29f3b9 Documentation/spi/spi-summary.rst Mauro Carvalho Chehab 2019-07-31 @2 ====================================
8ae12a0d85987d Documentation/spi/spi-summary David Brownell 2006-01-08 3 Overview of Linux kernel SPI support
8ae12a0d85987d Documentation/spi/spi-summary David Brownell 2006-01-08 4 ====================================
8ae12a0d85987d Documentation/spi/spi-summary David Brownell 2006-01-08 5
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-06-11 8:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 0:32 [PATCH] Documentation: spi: add SPDX license identifier Diogo Pimenta
2026-06-11 0:32 ` [PATCH] Documentation: spi: clarify clock modes question heading Diogo Pimenta
2026-06-11 8:51 ` kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-06-11 0:15 [PATCH] Documentation: spi: add SPDX license identifier Diogo Pimenta
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=202606111027.TFnhhj2n-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=diogo2003.pimenta@gmail.com \
--cc=diogo2003pimenta@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@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