From: kernel test robot <lkp@intel.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-doc@vger.kernel.org
Subject: [cel:topic-rpc-with-tls-upcall 2/19] htmldocs: Documentation/networking/tls-handshake.rst:53: WARNING: Inline emphasis start-string without end-string.
Date: Fri, 17 Mar 2023 09:12:18 +0800 [thread overview]
Message-ID: <202303170958.XI9RY3AN-lkp@intel.com> (raw)
tree: git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux topic-rpc-with-tls-upcall
head: 12050f1a9e648a9a557c8e5b1c635a2af6a29202
commit: 1daef8af2deecd9c894b8621cc1e833f293821da [2/19] net/tls: Add kernel APIs for requesting a TLSv1.3 handshake
reproduce:
# https://git.kernel.org/pub/scm/linux/kernel/git/cel/linux.git/commit/?id=1daef8af2deecd9c894b8621cc1e833f293821da
git remote add cel git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux
git fetch --no-tags cel topic-rpc-with-tls-upcall
git checkout 1daef8af2deecd9c894b8621cc1e833f293821da
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/202303170958.XI9RY3AN-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> Documentation/networking/tls-handshake.rst:53: WARNING: Inline emphasis start-string without end-string.
>> Documentation/networking/tls-handshake.rst:62: WARNING: Definition list ends without a blank line; unexpected unindent.
vim +53 Documentation/networking/tls-handshake.rst
51
52 struct tls_handshake_args {
> 53 struct socket *ta_sock;
54 tls_done_func_t ta_done;
55 void *ta_data;
56 unsigned int ta_timeout_ms;
57 key_serial_t ta_keyring;
58 key_serial_t ta_my_cert;
59 key_serial_t ta_my_privkey;
60 unsigned int ta_num_peerids;
61 key_serial_t ta_my_peerids[5];
> 62 };
63
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-03-17 1: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=202303170958.XI9RY3AN-lkp@intel.com \
--to=lkp@intel.com \
--cc=chuck.lever@oracle.com \
--cc=linux-doc@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;
as well as URLs for NNTP newsgroup(s).