From: "Tobin C. Harding" <me@tobin.cc>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND net-next] docs: net: Convert tcp.txt to RST format
Date: Wed, 12 Sep 2018 08:25:55 +1000 [thread overview]
Message-ID: <20180911222555.GD3854@eros> (raw)
In-Reply-To: <7f50abcd-f2fa-c043-9e5b-8e5ca89c52a1@gmail.com>
On Tue, Sep 11, 2018 at 03:30:19AM -0700, Eric Dumazet wrote:
>
>
> On 09/11/2018 12:13 AM, Tobin C. Harding wrote:
> > Restructured text is the kernel documentation format of choice now.
> > Some text from tcp.txt is out of date, specifically the function
> > tcp_write() does not appear to be in the tree anymore. Also the
> > following data members have been removed
> >
> > sk->tcp_pend_event
> > sk->transmit_queue
> > sk->transmit_new
> > sk->transmit_end
> > sk->tcp_last_tx_ack
> > sk->tcp_dup_ack
> >
> > Remove section 'How the new TCP output machine [nyi] works'. This
> > leaves only a single section so we can name the document with that
> > section heading now.
> >
> > Convert tcp.txt to RST format. Add GPLv2 SPDX tag.
> >
> > Signed-off-by: Tobin C. Harding <me@tobin.cc>
> >
>
> I dunno, this 'doc' is probably useless and should be deleted.
Cool! The best type of patch - line removal only. I'll put it in.
thanks,
Tobin.
prev parent reply other threads:[~2018-09-11 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 7:13 [PATCH RESEND net-next] docs: net: Convert tcp.txt to RST format Tobin C. Harding
2018-09-11 10:30 ` Eric Dumazet
2018-09-11 22:25 ` Tobin C. Harding [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=20180911222555.GD3854@eros \
--to=me@tobin.cc \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.