From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, sfr@canb.auug.org.au, corbet@lwn.net,
przemyslaw.kitszel@intel.com, tariqt@nvidia.com,
saeedm@nvidia.com, linux-doc@vger.kernel.org
Subject: Re: [PATCH net] docs: networking: fix indentation errors in multi-pf-netdev
Date: Thu, 14 Mar 2024 12:30:28 +0000 [thread overview]
Message-ID: <171041942842.26728.5742592401938580391.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240313032329.3919036-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Tue, 12 Mar 2024 20:23:29 -0700 you wrote:
> Stephen reports new warnings in the docs:
>
> Documentation/networking/multi-pf-netdev.rst:94: ERROR: Unexpected indentation.
> Documentation/networking/multi-pf-netdev.rst:106: ERROR: Unexpected indentation.
>
> Fixes: 77d9ec3f6c8c ("Documentation: networking: Add description for multi-pf netdev")
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Link: https://lore.kernel.org/all/20240312153304.0ef1b78e@canb.auug.org.au/
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>
> [...]
Here is the summary with links:
- [net] docs: networking: fix indentation errors in multi-pf-netdev
https://git.kernel.org/netdev/net/c/1c6368679979
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:[~2024-03-14 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 3:23 [PATCH net] docs: networking: fix indentation errors in multi-pf-netdev Jakub Kicinski
2024-03-13 6:07 ` Tariq Toukan
2024-03-13 8:03 ` Yunsheng Lin
2024-03-13 9:32 ` Jonathan Corbet
2024-03-14 12:30 ` 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=171041942842.26728.5742592401938580391.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=saeedm@nvidia.com \
--cc=sfr@canb.auug.org.au \
--cc=tariqt@nvidia.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).