All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com,
	Guenter Roeck <groeck@google.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [chrome-os:chromeos-5.4 19/68] htmldocs: Documentation/firmware-guide/acpi/chromeos-acpi-device.rst:134: WARNING: Error in "code-block" directive:
Date: Sat, 2 Sep 2023 08:11:31 +0800	[thread overview]
Message-ID: <202309020831.eFrJqpRs-lkp@intel.com> (raw)

tree:   https://chromium.googlesource.com/chromiumos/third_party/kernel chromeos-5.4
head:   cc41bfc48073553c102f0d6fd950190af1e79fe7
commit: 769e0664ecc37eb6234b03730c645b2bfd522d4a [19/68] BACKPORT: platform/chrome: Add ChromeOS ACPI device driver
reproduce: (https://download.01.org/0day-ci/archive/20230902/202309020831.eFrJqpRs-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/202309020831.eFrJqpRs-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Documentation/firmware-guide/acpi/chromeos-acpi-device.rst:134: WARNING: Error in "code-block" directive:

vim +134 Documentation/firmware-guide/acpi/chromeos-acpi-device.rst

   133	
 > 134	.. code-block::
   135	
   136	   Package {
   137	           Reserved1
   138	           Reserved2
   139	           Active EC Firmware
   140	           Active Main Firmware Type
   141	           Reserved5
   142	   }
   143	

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

                 reply	other threads:[~2023-09-02  0:12 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=202309020831.eFrJqpRs-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=cros-kernel-buildreports@googlegroups.com \
    --cc=groeck@google.com \
    --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 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.