From: kernel test robot <lkp@intel.com>
To: Jack Rosenthal <jrosenth@chromium.org>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
0day robot <lkp@intel.com>,
linux-doc@vger.kernel.org
Subject: htmldocs: Documentation/ABI/testing/sysfs-firmware-coreboot:2: WARNING: Definition list ends without a blank line; unexpected unindent.
Date: Sat, 30 Jul 2022 17:56:57 +0800 [thread overview]
Message-ID: <202207301713.q4988FIe-lkp@intel.com> (raw)
tree: https://github.com/intel-lab-lkp/linux/commits/UPDATE-20220730-033257/Jack-Rosenthal/firmware-google-Implement-vboot-workbuf-in-sysfs/20220727-075259
head: 7271f1344693f4e86debf8ae58f81ea50f3756c4
commit: 7271f1344693f4e86debf8ae58f81ea50f3756c4 firmware: google: Implement cbmem in sysfs driver
date: 14 hours ago
reproduce: make htmldocs
If you fix the issue, kindly add following tag where applicable
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> Documentation/ABI/testing/sysfs-firmware-coreboot:2: WARNING: Definition list ends without a blank line; unexpected unindent.
>> Documentation/ABI/testing/sysfs-firmware-coreboot:2: WARNING: Unexpected indentation.
>> Documentation/ABI/testing/sysfs-firmware-coreboot:2: WARNING: Block quote ends without a blank line; unexpected unindent.
vim +2 Documentation/ABI/testing/sysfs-firmware-coreboot
> 2 Date: July 2022
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next reply other threads:[~2022-07-30 9:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 9:56 kernel test robot [this message]
2022-08-01 15:26 ` [PATCH v5] firmware: google: Implement cbmem in sysfs driver Jack Rosenthal
2022-08-01 22:14 ` Julius Werner
2022-08-02 14:03 ` [PATCH v6] " Jack Rosenthal
2022-08-02 14:37 ` Guenter Roeck
2022-08-04 8:22 ` Tzung-Bi Shih
2022-08-04 14:28 ` [PATCH v7] " Jack Rosenthal
2022-08-04 20:59 ` Stephen Boyd
2022-08-04 23:14 ` Julius Werner
2022-08-10 16:40 ` Stephen Boyd
2022-08-10 22:26 ` Julius Werner
2022-08-10 23:58 ` Stephen Boyd
2022-08-11 1:17 ` Julius Werner
2022-08-06 20:46 ` Jack Rosenthal
2022-08-04 14:31 ` [PATCH v6] " Jack Rosenthal
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=202207301713.q4988FIe-lkp@intel.com \
--to=lkp@intel.com \
--cc=jrosenth@chromium.org \
--cc=kbuild-all@lists.01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.