From: Greg KH <gregkh@linuxfoundation.org>
To: Harald Freudenberger <freude@linux.ibm.com>
Cc: akrowiak@linux.ibm.com, schwidefsky@de.ibm.com, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] s390/zcrypt: reinit ap queue state machine during device" failed to apply to 4.19-stable tree
Date: Thu, 6 Dec 2018 12:31:03 +0100 [thread overview]
Message-ID: <20181206113103.GA13357@kroah.com> (raw)
In-Reply-To: <3ec0ae07-c754-f5bf-a6c1-8190c52bd4ff@linux.ibm.com>
On Thu, Dec 06, 2018 at 12:14:59PM +0100, Harald Freudenberger wrote:
> On 06.12.18 09:57, 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
> >
> > ------------------ original commit in Linus's tree ------------------
> >
> > From 104f708fd1241b22f808bdf066ab67dc5a051de5 Mon Sep 17 00:00:00 2001
> > From: Harald Freudenberger <freude@linux.ibm.com>
> > Date: Fri, 9 Nov 2018 14:59:24 +0100
> > Subject: [PATCH] s390/zcrypt: reinit ap queue state machine during device
> > probe
>
> <rest of the patch removed>
>
> This fix is not needed for the 4.19 stable tree as there is no exploiter
> for the ap mask feature in that kernel. The exploiter will come with
> the vfio device driver for the ap bus which went into the 4.20 kernel.
Great, thanks for letting me know.
greg k-h
prev parent reply other threads:[~2018-12-06 11:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 8:57 FAILED: patch "[PATCH] s390/zcrypt: reinit ap queue state machine during device" failed to apply to 4.19-stable tree gregkh
2018-12-06 11:14 ` Harald Freudenberger
2018-12-06 11:31 ` 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=20181206113103.GA13357@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akrowiak@linux.ibm.com \
--cc=freude@linux.ibm.com \
--cc=schwidefsky@de.ibm.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.