From: Greg KH <gregkh@linuxfoundation.org>
To: Don Dutile <ddutile@redhat.com>
Cc: chuck.lever@oracle.com, bfields@redhat.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] svcrdma: Remove max_sge check at connect time" failed to apply to 4.19-stable tree
Date: Wed, 13 Feb 2019 16:39:18 +0100 [thread overview]
Message-ID: <20190213153918.GA7696@kroah.com> (raw)
In-Reply-To: <611fdd86-2b69-3be9-078a-d57fc126c601@redhat.com>
On Wed, Feb 13, 2019 at 10:19:35AM -0500, Don Dutile wrote:
> On 02/13/2019 08:46 AM, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 4.19-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
> >
> > thanks,
> >
> > greg k-h
> >
> It also needs this patch (from v4.20) applied for it to cleanly apply to v4.19:
> commit f3c1fd0ee294abd4367dfa72d89f016c682202f0
> Author: Chuck Lever <chuck.lever@oracle.com>
> Date: Mon Oct 1 14:15:56 2018 -0400
>
> svcrdma: Reduce max_send_sges
> There's no need to request a large number of send SGEs because the
> inline threshold already constrains the number of SGEs per Send.
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
>
>
>
>
> [ddutile@dddlaptop linux]$ git tag --contains !$
> git tag --contains f3c1fd0ee294abd4367dfa72d89f016c682202f0
> v4.20
> ....
Thanks, that worked!
greg k-h
prev parent reply other threads:[~2019-02-13 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-13 13:46 FAILED: patch "[PATCH] svcrdma: Remove max_sge check at connect time" failed to apply to 4.19-stable tree gregkh
2019-02-13 15:19 ` Don Dutile
2019-02-13 15:39 ` 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=20190213153918.GA7696@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bfields@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=ddutile@redhat.com \
--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).