All of lore.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Laura Abbott <labbott@redhat.com>
Cc: Ilya Leoshkevich <iii@linux.ibm.com>,
	stable <stable@vger.kernel.org>,
	Major Hayden <mhayden@redhat.com>
Subject: Re: Request for 4.19.x backport (with conflicts)
Date: Fri, 21 Jun 2019 15:11:35 +0200	[thread overview]
Message-ID: <20190621131135.GB11296@osiris> (raw)
In-Reply-To: <0fc1a3e6-59ef-6390-38c4-55e7c48bee78@redhat.com>

Hello Laura,

> We're attempting to build stable kernels with gcc9. 4.19.x fails to build with
> gcc9 as 146448524bdd ("s390/jump_label: Use "jdd" constraint on gcc9") is missing.
> This doesn't apply cleanly to 4.19.x as it needs changes from 13ddb52c165b
> ("s390/jump_label: Switch to relative references")
> 
> Which is better, taking both 13ddb52c165b and 146448524bdd or doing
> a backport of 146448524bdd?

I don't know which kernel version you are referring to exactly,
however 4.19.53 from linux-stable does not contain the common code
infrastructure for relative jump labels. The infrastructure was merged
with 4.20: commit 50ff18ab497aa ("jump_label: Implement generic
support for relative references").

Therefore a backport of only 146448524bdd seems to be the way to go.


  reply	other threads:[~2019-06-21 13:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21 12:51 Request for 4.19.x backport (with conflicts) Laura Abbott
2019-06-21 13:11 ` Heiko Carstens [this message]
2019-06-21 14:48   ` Laura Abbott
2019-06-21 15:39     ` [PATCH] s390/jump_label: Use "jdd" constraint on gcc9 Ilya Leoshkevich
2019-06-21 17:46       ` Laura Abbott
2019-06-23  2:00         ` Sasha Levin

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=20190621131135.GB11296@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=iii@linux.ibm.com \
    --cc=labbott@redhat.com \
    --cc=mhayden@redhat.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.