netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ncardwell@google.com
Cc: ilpo.jarvinen@helsinki.fi, gregkh@linuxfoundation.org,
	netdev@vger.kernel.org, nanditad@google.com, ycheng@google.com,
	therbert@google.com, subramanian.vijay@gmail.com
Subject: Re: [PATCH] tcp: fix tcp_shifted_skb() adjustment of lost_cnt_hint for FACK
Date: Mon, 27 Feb 2012 21:58:20 -0500 (EST)	[thread overview]
Message-ID: <20120227.215820.1289745868005567561.davem@davemloft.net> (raw)
In-Reply-To: <CADVnQym_a=QDyjGX=L6-o3orxPdKJOwVZNfutaW5ZHAt=aB21A@mail.gmail.com>

From: Neal Cardwell <ncardwell@google.com>
Date: Mon, 27 Feb 2012 21:40:03 -0500

> Yes, I agree that it would make sense to hold off on adding these
> three 3.3-rc4 commits to the stable tree:
> 
> cc9a672ee522d4805495b98680f4a3db5d0a0af9
> 
> daef52bab1fd26e24e8e9578f8fb33ba1d0cb412
> 
> 0af2a0d0576205dda778d25c6c344fc6508fc81d
> 
> It would make sense to let the dust settle a bit more before adding
> those to the stable tree.
> 
> The same goes for the http://patchwork.ozlabs.org/patch/143114/ patch
> (under review) that is in the same area of the code.

I totally disagree and I have submitted those fixes to -stable
already and do not plan to rescind those submissions at all.

  reply	other threads:[~2012-02-28  2:58 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14  6:22 [PATCH] tcp: fix tcp_shifted_skb() adjustment of lost_cnt_hint for FACK Neal Cardwell
2012-02-14 19:40 ` David Miller
2012-02-14 19:41   ` David Miller
2012-02-27 23:39   ` Ilpo Järvinen
2012-02-27 23:43     ` Ilpo Järvinen
2012-02-28  2:40       ` Neal Cardwell
2012-02-28  2:58         ` David Miller [this message]
2012-02-28  3:45           ` Neal Cardwell
2012-02-28  4:31             ` David Miller
2012-02-28  4:42               ` Neal Cardwell

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=20120227.215820.1289745868005567561.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=nanditad@google.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=subramanian.vijay@gmail.com \
    --cc=therbert@google.com \
    --cc=ycheng@google.com \
    /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).