All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Michael Holzheu <holzheu@linux.vnet.ibm.com>
Cc: stable@vger.kernel.org, heiko.carstens@de.ibm.com,
	maier@linux.vnet.ibm.com, schwidefsky@de.ibm.com
Subject: Re: [PATCH] Revert "s390/kdump: Clear subchannel ID to signal non-CCW/SCSI IPL"
Date: Sun, 14 Aug 2016 17:15:59 +0200	[thread overview]
Message-ID: <20160814151559.GC20560@kroah.com> (raw)
In-Reply-To: <20160726135132.51c2d872@TP-holzheu>

On Tue, Jul 26, 2016 at 01:51:32PM +0200, Michael Holzheu wrote:
> My mailer re-formatted the patch. Sorry for that.
> 
> Second try:
> 
> This reverts commit 852ffd0f4e23248b47531058e531066a988434b5.
> 
> There are use cases where an intermediate boot kernel (1) uses kexec
> to boot the final production kernel (2). For this scenario we should
> provide the original boot information to the production kernel (2).
> Therefore clearing the boot information during kexec() should not
> be done.
> 
> Cc: stable@vger.kernel.org # v3.17+
> Reported-by: Steffen Maier <maier@linux.vnet.ibm.com>
> Signed-off-by: Michael Holzheu <holzheu@linux.vnet.ibm.com>
> Reviewed-by: Heiko Carstens <heiko.carstens@de.ibm.com>
> Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com
> ---
> * Requested versions for stable: v3.17 - v4.4
> * Changes for v3.17 - v4.4 stable:
>   - Refresh patch to fit to new context

Please always remind us what the upstream commit was for the patch (it
was 5419447e2142d6ed68c9f5c1a28630b3a290a845, right?)

thanks,

greg k-h

  reply	other threads:[~2016-08-14 15:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-25  0:57 FAILED: patch "[PATCH] Revert "s390/kdump: Clear subchannel ID to signal" failed to apply to 4.4-stable tree gregkh
2016-07-26 11:43 ` [PATCH] Revert "s390/kdump: Clear subchannel ID to signal non-CCW/SCSI IPL" Michael Holzheu
2016-07-26 11:51   ` Michael Holzheu
2016-08-14 15:15     ` Greg KH [this message]
2016-08-15 13:17       ` Michael Holzheu

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=20160814151559.GC20560@kroah.com \
    --to=greg@kroah.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=holzheu@linux.vnet.ibm.com \
    --cc=maier@linux.vnet.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.