From: Heiko Carstens <hca@linux.ibm.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
Sven Schnelle <svens@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>
Subject: Re: [PATCH 1/2] scripts/min-tool-version.sh: Raise minimum clang version to 19.1.0 for s390
Date: Thu, 14 Nov 2024 18:05:24 +0100 [thread overview]
Message-ID: <20241114170524.9691-B-hca@linux.ibm.com> (raw)
In-Reply-To: <20241113182109.GA3713382@thelio-3990X>
On Wed, Nov 13, 2024 at 11:21:09AM -0700, Nathan Chancellor wrote:
> On Wed, Nov 13, 2024 at 04:40:12PM +0100, Heiko Carstens wrote:
> > Raise minimum clang version to 19.1.0 for s390 so that various inline
> > assembly format flags can be used. The missing format flags were
> > implemented with llvm-project commit 9c75a981554d ("[SystemZ] Implement A,
> > O and R inline assembly format flags (#80685)").
> >
> > Signed-off-by: Heiko Carstens <hca@linux.ibm.com>
>
> Oof, this is quite new but now that kernel.org has LLVM binaries
> available, I do not think this is an unreasonable ask, especially if it
> makes your life easier with code maintenance.
Thanks for your feedback! I read this as "is nearly unreasonable" :)
Even though you acked this, I guess I will drop this for now and
maybe address this a few clang versions later.
next prev parent reply other threads:[~2024-11-14 17:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 15:40 [PATCH 0/2] s390: Raise minimum clang version to 19.1.0 Heiko Carstens
2024-11-13 15:40 ` [PATCH 1/2] scripts/min-tool-version.sh: Raise minimum clang version to 19.1.0 for s390 Heiko Carstens
2024-11-13 18:21 ` Nathan Chancellor
2024-11-14 17:05 ` Heiko Carstens [this message]
2024-11-14 17:25 ` Nathan Chancellor
2024-11-13 15:40 ` [PATCH 2/2] s390/fpu: Remove inline assembly variants for old clang versions Heiko Carstens
2024-11-13 18:22 ` Nathan Chancellor
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=20241114170524.9691-B-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--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