From: Jeremy Sowden <jeremy@azazel.net>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Netfilter Devel <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH] docs: nf_flowtable: fix typo.
Date: Sun, 18 Oct 2020 16:32:39 +0100 [thread overview]
Message-ID: <20201018153239.GA349273@ulthar.dreamlands> (raw)
In-Reply-To: <20201018153019.350400-1-jeremy@azazel.net>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
On 2020-10-18, at 16:30:19 +0100, Jeremy Sowden wrote:
> "mailined" should be "mainlined."
>
> Signed-off-by: Jeremy Sowden <jeremy@azazel.net>
> ---
> Documentation/networking/nf_flowtable.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/networking/nf_flowtable.rst b/Documentation/networking/nf_flowtable.rst
> index b6e1fa141aae..6cdf9a1724b6 100644
> --- a/Documentation/networking/nf_flowtable.rst
> +++ b/Documentation/networking/nf_flowtable.rst
> @@ -109,7 +109,7 @@ More reading
> This documentation is based on the LWN.net articles [1]_\ [2]_. Rafal Milecki
> also made a very complete and comprehensive summary called "A state of network
> acceleration" that describes how things were before this infrastructure was
> -mailined [3]_ and it also makes a rough summary of this work [4]_.
> +mainlined [3]_ and it also makes a rough summary of this work [4]_.
>
> .. [1] https://lwn.net/Articles/738214/
> .. [2] https://lwn.net/Articles/742164/
Forgot to include the tree in the subject. The patch was intended for
nf-next.
J.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2020-10-18 15:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 15:30 [PATCH] docs: nf_flowtable: fix typo Jeremy Sowden
2020-10-18 15:32 ` Jeremy Sowden [this message]
2020-10-20 15:19 ` Pablo Neira Ayuso
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=20201018153239.GA349273@ulthar.dreamlands \
--to=jeremy@azazel.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
/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).