Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jchapman@katalix.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v2] Documentation/networking: update l2tp docs
Date: Wed, 19 Aug 2020 12:56:40 -0700 (PDT)	[thread overview]
Message-ID: <20200819.125640.1848130299373351106.davem@davemloft.net> (raw)
In-Reply-To: <20200819092032.23198-1-jchapman@katalix.com>

From: jchapman@katalix.com
Date: Wed, 19 Aug 2020 10:20:32 +0100

> From: James Chapman <jchapman@katalix.com>
> 
> Kernel documentation of L2TP has not been kept up to date and lacks
> coverage of some L2TP APIs. While addressing this, refactor to improve
> readability, separating the parts which focus on user APIs and
> internal implementation into sections.
> 
> Changes in v2:
> 
>  - fix checkpatch warnings about trailing whitespace and long lines
> 
> Signed-off-by: James Chapman <jchapman@katalix.com>

Applied, thanks James.

      reply	other threads:[~2020-08-19 19:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-19  9:20 jchapman
2020-08-19 19:56 ` David Miller [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=20200819.125640.1848130299373351106.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jchapman@katalix.com \
    --cc=netdev@vger.kernel.org \
    --subject='Re: [PATCH net-next v2] Documentation/networking: update l2tp docs' \
    /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

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).