From: Simon Horman <horms@kernel•org>
To: Bagas Sanjaya <bagasdotme@gmail•com>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Documentation <linux-doc@vger•kernel.org>,
Linux Networking <netdev@vger•kernel.org>,
Sridhar Samudrala <sridhar.samudrala@intel•com>,
"David S. Miller" <davem@davemloft•net>,
Eric Dumazet <edumazet@google•com>,
Jakub Kicinski <kuba@kernel•org>, Paolo Abeni <pabeni@redhat•com>,
Jonathan Corbet <corbet@lwn•net>,
Krishna Kumar <krikku@gmail•com>,
Vasudev Kamath <vasudev@copyninja•info>
Subject: Re: [PATCH net v2] Documentation: net: net_failover: Separate cloud-ifupdown-helper and reattach-vf.sh code blocks marker
Date: Thu, 16 Oct 2025 16:51:38 +0100 [thread overview]
Message-ID: <aPEUiuelF8LSBmdi@horms.kernel.org> (raw)
In-Reply-To: <20251016093936.29442-2-bagasdotme@gmail.com>
On Thu, Oct 16, 2025 at 04:39:37PM +0700, Bagas Sanjaya wrote:
> cloud-ifupdown-helper patch and reattach-vf.sh script are rendered in
> htmldocs output as normal paragraphs instead of literal code blocks
> due to missing separator from respective code block marker. Add it.
>
> Fixes: 738baea4970b ("Documentation: networking: net_failover: Fix documentation")
> Signed-off-by: Bagas Sanjaya <bagasdotme@gmail•com>
> ---
> Changes since v1 [1]:
>
> - Place code block marker at the end of previous paragraph (Simon)
>
> [1]: https://lore.kernel.org/linux-doc/20251015094502.35854-2-bagasdotme@gmail.com/
Thanks for the update.
Reviewed-by: Simon Horman <horms@kernel•org>
next prev parent reply other threads:[~2025-10-16 15:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 9:39 [PATCH net v2] Documentation: net: net_failover: Separate cloud-ifupdown-helper and reattach-vf.sh code blocks marker Bagas Sanjaya
2025-10-16 15:51 ` Simon Horman [this message]
2025-10-18 0:00 ` 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=aPEUiuelF8LSBmdi@horms.kernel.org \
--to=horms@kernel$(echo .)org \
--cc=bagasdotme@gmail$(echo .)com \
--cc=corbet@lwn$(echo .)net \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=krikku@gmail$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=linux-doc@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=sridhar.samudrala@intel$(echo .)com \
--cc=vasudev@copyninja$(echo .)info \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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