From: Greg KH <gregkh@linuxfoundation.org>
To: Jason Gunthorpe <jgg@mellanox.com>
Cc: Don Dutile <ddutile@redhat.com>,
danielj@mellanox.com, bharat@chelsio.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 23:21:08 +0100 [thread overview]
Message-ID: <20171211222108.GB22320@kroah.com> (raw)
In-Reply-To: <20171211215358.GG4797@mellanox.com>
On Mon, Dec 11, 2017 at 02:53:58PM -0700, Jason Gunthorpe wrote:
> On Mon, Dec 11, 2017 at 10:50:31PM +0100, Greg KH wrote:
> > 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
> >
> > That patch was not tagged for stable at all :(
>
> It doesn't look like something that should go to -stable to me..
>
> I think we will need to make you a proper 4.14 backport for the 'Only
> enforce security for InfiniBand' patch.
No, I almost always want the same exact patches that are in Linus's
tree. Otherwise the patch you make will be wrong 90% of the time.
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-11 22:21 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 [this message]
2017-12-11 21:51 ` Greg KH
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=20171211222108.GB22320@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.