All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, schwidefsky@de.ibm.com
Subject: Re: [PATCH/backport for 4.4] s390/cpumf: Fix lpp detection
Date: Wed, 16 Mar 2016 16:18:02 +0100	[thread overview]
Message-ID: <56E9792A.2090207@de.ibm.com> (raw)
In-Reply-To: <20160316151539.GA6720@kroah.com>

On 03/16/2016 04:15 PM, Greg KH wrote:
> On Wed, Mar 16, 2016 at 11:02:58AM +0100, Christian Borntraeger wrote:
>> we have to check bit 40 of the facility list before issuing LPP
>> and not bit 48. Otherwise a guest running on a system with
>> "The decimal-floating-point zoned-conversion facility" and without
>> the "The set-program-parameters facility" might crash on an lpp
>> instruction.
>>
>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>> Cc: stable@vger.kernel.org # v4.4+
>> Fixes: e22cf8ca6f75 ("s390/cpumf: rework program parameter setting to detect guest samples")
>> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com>
>> ---
>>  arch/s390/kernel/head64.S | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> What is the git commit id of this patch in Linus's tree?
> 
> thanks,
> 
> greg k-h
> 


>From 7a76aa95f6f6682db5629449d763251d1c9f8c4e Mon Sep 17 00:00:00 2001
From: Christian Borntraeger <borntraeger@de.ibm.com>
Date: Mon, 29 Feb 2016 15:59:18 +0100
Subject: [PATCH] s390/cpumf: Fix lpp detection

This is the fixup for you mail 
"FAILED: patch "[PATCH] s390/cpumf: Fix lpp detection" failed to apply to 4.4-stable tree"
from 03/12/2016


      reply	other threads:[~2016-03-16 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-16 10:02 [PATCH/backport for 4.4] s390/cpumf: Fix lpp detection Christian Borntraeger
2016-03-16 15:15 ` Greg KH
2016-03-16 15:18   ` Christian Borntraeger [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=56E9792A.2090207@de.ibm.com \
    --to=borntraeger@de.ibm.com \
    --cc=gregkh@linuxfoundation.org \
    --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.