From: Greg KH <gregkh@linuxfoundation.org>
To: Don Dutile <ddutile@redhat.com>
Cc: danielj@mellanox.com, bharat@chelsio.com, jgg@mellanox.com,
leon@kernel.org, parav@mellanox.com, paul@paul-moore.com,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] IB/core: Only enforce security for InfiniBand" failed to apply to 4.14-stable tree
Date: Mon, 11 Dec 2017 22:51:01 +0100 [thread overview]
Message-ID: <20171211215101.GB30276@kroah.com> (raw)
In-Reply-To: <13c9371d-98db-1d84-c2f8-4300e5334bc1@redhat.com>
On Mon, Dec 11, 2017 at 04:43:44PM -0500, Don Dutile wrote:
> On 12/11/2017 04:19 PM, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 4.14-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
> >
> That's b/c this patch needs to be applied (tagged for stable) first:
>
> commit 2e4c85c6edc80fa532b2c7e1eb3597ef4d4bbb8f
> Author: Parav Pandit <parav@mellanox.com>
> Date: Thu Nov 2 15:22:27 2017 +0200
>
> IB/core: Avoid unnecessary return value check
> Since there is nothing done with non zero return value, such check is
> avoided.
> Signed-off-by: Parav Pandit <parav@mellanox.com>
> Reviewed-by: Daniel Jurgens <danielj@mellanox.com>
> Signed-off-by: Leon Romanovsky <leon@kernel.org>
> Signed-off-by: Doug Ledford <dledford@redhat.com>
> 2b2c7e1eb3597ef4d4bbb8f
>
> All applied cleanly to RHEL when done in that order.
That worked, thanks.
greg k-h
prev parent reply other threads:[~2017-12-11 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 21:19 FAILED: patch "[PATCH] IB/core: Only enforce security for InfiniBand" failed to apply to 4.14-stable tree gregkh
2017-12-11 21:43 ` Don Dutile
2017-12-11 21:50 ` Greg KH
2017-12-11 21:53 ` Jason Gunthorpe
2017-12-11 22:21 ` Greg KH
2017-12-11 21:51 ` 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=20171211215101.GB30276@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bharat@chelsio.com \
--cc=danielj@mellanox.com \
--cc=ddutile@redhat.com \
--cc=jgg@mellanox.com \
--cc=leon@kernel.org \
--cc=parav@mellanox.com \
--cc=paul@paul-moore.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).