From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 1/3] tcp: Correction to RFC number in comment
Date: Thu, 30 Oct 2014 12:51:02 -0400 [thread overview]
Message-ID: <20141030165102.GI650@oracle.com> (raw)
In-Reply-To: <20141030.123235.2180775200364575758.davem@davemloft.net>
On (10/30/14 12:32), David Miller wrote:
>
> Please do not ever mix unrelated changes like this within a series.
>
> Submit the TCP change on it's own, and then respin the sunvnet
> driver specific patches separately.
Done.
fwiw, I ran into this comment when debugging something in sunvnet,
and was quite confused by the rfc 5691 reference :-)
--Sowmini
prev parent reply other threads:[~2014-10-30 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 19:27 [PATCH net-next 1/3] tcp: Correction to RFC number in comment Sowmini Varadhan
2014-10-30 16:32 ` David Miller
2014-10-30 16:51 ` Sowmini Varadhan [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=20141030165102.GI650@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=davem@davemloft.net \
--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).