netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tariq Toukan <ttoukan.linux@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>, davem@davemloft.net
Cc: netdev@vger.kernel.org, edumazet@google.com, pabeni@redhat.com,
	Stephen Rothwell <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: Wed, 13 Mar 2024 08:07:38 +0200	[thread overview]
Message-ID: <2ab5b453-494c-409b-82c4-f2c62adb43ca@gmail.com> (raw)
In-Reply-To: <20240313032329.3919036-1-kuba@kernel.org>



On 13/03/2024 5:23, Jakub Kicinski 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>
> ---
> Turns out our build test for docs was broken.
> ---
> CC: corbet@lwn.net
> CC: przemyslaw.kitszel@intel.com
> CC: tariqt@nvidia.com
> CC: saeedm@nvidia.com
> CC: linux-doc@vger.kernel.org

Thanks for taking care of this.
Reviewed-by: Tariq Toukan <tariqt@nvidia.com>


  reply	other threads:[~2024-03-13  6:07 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 [this message]
2024-03-13  8:03 ` Yunsheng Lin
2024-03-13  9:32   ` Jonathan Corbet
2024-03-14 12:30 ` patchwork-bot+netdevbpf

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=2ab5b453-494c-409b-82c4-f2c62adb43ca@gmail.com \
    --to=ttoukan.linux@gmail.com \
    --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).