From: patchwork-bot+netdevbpf@kernel.org
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, oe-kbuild-all@lists.linux.dev,
gwml@vger.gnuweeb.org, lkp@intel.com, jiri@nvidia.com,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, corbet@lwn.net, michal.wilczynski@intel.com,
ammarfaizi2@gnuweeb.org
Subject: Re: [PATCH net-next] Documentation: devlink: Add blank line padding on numbered lists in Devlink Port documentation
Date: Wed, 23 Nov 2022 12:50:15 +0000 [thread overview]
Message-ID: <166920781551.7047.17657573305612000567.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221121035854.28411-1-bagasdotme@gmail.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Mon, 21 Nov 2022 10:58:55 +0700 you wrote:
> kernel test robot reported indentation warnings:
>
> Documentation/networking/devlink/devlink-port.rst:220: WARNING: Unexpected indentation.
> Documentation/networking/devlink/devlink-port.rst:222: WARNING: Block quote ends without a blank line; unexpected unindent.
>
> These warnings cause lists (arbitration flow for which the warnings blame to
> and 3-step subfunction setup) to be rendered inline instead. Also, for the
> former list, automatic list numbering is messed up.
>
> [...]
Here is the summary with links:
- [net-next] Documentation: devlink: Add blank line padding on numbered lists in Devlink Port documentation
https://git.kernel.org/netdev/net-next/c/c84f6f6c2bb5
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-11-23 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <202211200926.kfOPiVti-lkp@intel.com>
2022-11-21 3:58 ` [PATCH net-next] Documentation: devlink: Add blank line padding on numbered lists in Devlink Port documentation Bagas Sanjaya
2022-11-23 12:50 ` patchwork-bot+netdevbpf [this message]
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=166920781551.7047.17657573305612000567.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gwml@vger.gnuweeb.org \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=michal.wilczynski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
/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).