stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: stable@vger.kernel.org,
	Benjamin Gilbert <benjamin.gilbert@coreos.com>,
	Eric Dumazet <edumazet@google.com>,
	"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH] tcp: do not overshoot window_clamp in tcp_rcv_space_adjust()
Date: Mon, 18 Jun 2018 09:09:29 +0200	[thread overview]
Message-ID: <20180618070929.GA2564@kroah.com> (raw)
In-Reply-To: <e3cfc46b-7a52-b876-1852-ee7137059edb@roeck-us.net>

On Sun, Jun 17, 2018 at 10:38:54PM -0700, Guenter Roeck wrote:
> This is supposed to be a backport for v4.14.y and older. Sorry for the confusion.

Not a problem, thanks for the patch, now queued up.

greg k-h

      reply	other threads:[~2018-06-18  7:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18  5:37 [PATCH] tcp: do not overshoot window_clamp in tcp_rcv_space_adjust() Guenter Roeck
2018-06-18  5:38 ` Guenter Roeck
2018-06-18  7:09   ` Greg KH [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=20180618070929.GA2564@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=benjamin.gilbert@coreos.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=linux@roeck-us.net \
    --cc=stable@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).