netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Tobin C. Harding" <me@tobin.cc>,
	"David S. Miller" <davem@davemloft.net>
Cc: 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: Tue, 11 Sep 2018 03:30:19 -0700	[thread overview]
Message-ID: <7f50abcd-f2fa-c043-9e5b-8e5ca89c52a1@gmail.com> (raw)
In-Reply-To: <20180911071324.11199-1-me@tobin.cc>



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.

  reply	other threads:[~2018-09-11 10:30 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 [this message]
2018-09-11 22:25   ` Tobin C. Harding

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=7f50abcd-f2fa-c043-9e5b-8e5ca89c52a1@gmail.com \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=me@tobin.cc \
    --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 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).