From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
James Chapman <jchapman@katalix.com>,
tparkin@katalix.com, edumazet@google.com, davem@davemloft.net,
kuba@kernel.org, pabeni@redhat.com, corbet@lwn.net,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2] PPPoL2TP: Add more code snippets
Date: Wed, 19 Apr 2023 15:27:50 +0700 [thread overview]
Message-ID: <ZD+mBrxdX8zugyO+@debian.me> (raw)
In-Reply-To: <20230418143307.hth4yjkopy5se4md@begin>
[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]
On Tue, Apr 18, 2023 at 04:33:07PM +0200, Samuel Thibault wrote:
> + - L2TP session bridging (also called L2TP tunnel switching or L2TP multihop)
> +is supported by bridging the ppp channels of the two L2TP sessions to be
> +bridged::
> +
The list text isn't aligned, hence Sphinx warning:
Documentation/networking/l2tp.rst:475: WARNING: Block quote ends without a blank line; unexpected unindent.
I have applied the fixup:
---- >8 ----
diff --git a/Documentation/networking/l2tp.rst b/Documentation/networking/l2tp.rst
index 3664d95268c9cc..e4c67f29e3639d 100644
--- a/Documentation/networking/l2tp.rst
+++ b/Documentation/networking/l2tp.rst
@@ -472,8 +472,8 @@ RTM_NEWLINK, RTM_NEWADDR, RTM_NEWROUTE, or ioctl's SIOCSIFMTU, SIOCSIFADDR,
SIOCSIFDSTADDR, SIOCSIFNETMASK, SIOCSIFFLAGS, or with the `ip` command.
- L2TP session bridging (also called L2TP tunnel switching or L2TP multihop)
-is supported by bridging the ppp channels of the two L2TP sessions to be
-bridged::
+ is supported by bridging the ppp channels of the two L2TP sessions to be
+ bridged::
int chindx1;
int chindx2;
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2023-04-19 8:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 14:33 [PATCHv2] PPPoL2TP: Add more code snippets Samuel Thibault
2023-04-19 8:27 ` Bagas Sanjaya [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=ZD+mBrxdX8zugyO+@debian.me \
--to=bagasdotme@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jchapman@katalix.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=tparkin@katalix.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).