public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Ingo Molnar <mingo@redhat.com>,
	Naresh Kamboju <naresh.kamboju@linaro.org>,
	Anders Roxell <anders.roxell@linaro.org>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>,
	Sven Schnelle <svens@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Christian Borntraeger <borntraeger@linux.ibm.com>,
	linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [PATCH 0/2] bugs/s390: Fix compile error with old gcc versions
Date: Tue, 17 Jun 2025 15:50:40 +0200	[thread overview]
Message-ID: <20250617135042.1878068-1-hca@linux.ibm.com> (raw)

As reported by Naresh and Anders old gcc variants cannot handle
strings as input operands for inline assemblies. Rewrite the s390
generic bug support very similar to arm64 and loongarch to fix this.

Also use the opportunity to drop the rather pointless s390 specific
WARN_ON() implementation.

Ingo, I think the two patches should also go via the core/bugs branch
of the tip repository.

Thanks,
Heiko

Heiko Carstens (2):
  bugs/s390: Remove private WARN_ON() implementation
  bugs/s390: Use inline assembly without input operands

 arch/s390/include/asm/bug.h | 94 ++++++++++++++++---------------------
 1 file changed, 41 insertions(+), 53 deletions(-)

-- 
2.48.1


             reply	other threads:[~2025-06-17 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 13:50 Heiko Carstens [this message]
2025-06-17 13:50 ` [PATCH 1/2] bugs/s390: Remove private WARN_ON() implementation Heiko Carstens
2025-06-20 13:15   ` Alexander Gordeev
2025-06-17 13:50 ` [PATCH 2/2] bugs/s390: Use inline assembly without input operands Heiko Carstens
2025-06-20 13:15   ` Alexander Gordeev
2025-06-25  9:31 ` [PATCH 0/2] bugs/s390: Fix compile error with old gcc versions Heiko Carstens

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=20250617135042.1878068-1-hca@linux.ibm.com \
    --to=hca@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=anders.roxell@linaro.org \
    --cc=borntraeger@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=naresh.kamboju@linaro.org \
    --cc=svens@linux.ibm.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox