From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android11-5.4 375/25663] htmldocs: Documentation/driver-api/driver-model/driver.rst:215: WARNING: Inline emphasis start-string without end-string.
Date: Sat, 25 Mar 2023 23:35:13 +0800 [thread overview]
Message-ID: <202303252345.oHz4eLyo-lkp@intel.com> (raw)
Hi Saravana,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android11-5.4
head: 13e656b3b5d58dcb8b2f70a368547be9c06a5143
commit: 2d4a45a8388023a4a1f35813cad0e2bab225047b [375/25663] FROMGIT: docs: driver-model: Add documentation for sync_state
reproduce:
git remote add android-common https://android.googlesource.com/kernel/common
git fetch --no-tags android-common android11-5.4
git checkout 2d4a45a8388023a4a1f35813cad0e2bab225047b
make menuconfig
# enable CONFIG_COMPILE_TEST, CONFIG_WARN_MISSING_DOCUMENTS, CONFIG_WARN_ABI_ERRORS
make htmldocs
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303252345.oHz4eLyo-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/driver-api/driver-model/driver.rst:215: WARNING: Inline emphasis start-string without end-string.
vim +215 Documentation/driver-api/driver-model/driver.rst
2d4a45a8388023 Documentation/driver-api/driver-model/driver.rst Saravana Kannan 2019-10-11 214
^1da177e4c3f41 Documentation/driver-model/driver.txt Linus Torvalds 2005-04-16 @215 int (*remove) (struct device *dev);
^1da177e4c3f41 Documentation/driver-model/driver.txt Linus Torvalds 2005-04-16 216
:::::: The code at line 215 was first introduced by commit
:::::: 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Linux-2.6.12-rc2
:::::: TO: Linus Torvalds <torvalds@ppc970.osdl.org>
:::::: CC: Linus Torvalds <torvalds@ppc970.osdl.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-03-25 15:36 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=202303252345.oHz4eLyo-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.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.