public inbox for linux-sparse@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-sparse@vger.kernel.org
Subject: Re: [PATCH 1/2] RISC-V: Stop warning about Zabha and Zacas
Date: Wed, 7 Jan 2026 13:41:18 -0700 (MST)	[thread overview]
Message-ID: <c5021639-ca56-67cc-ccb5-e074e60bb19d@kernel.org> (raw)
In-Reply-To: <20260102114449.535597-2-ben.dooks@codethink.co.uk>

On Fri, 2 Jan 2026, Ben Dooks wrote:

> The zabha (atomic byte and halfword) and zacas (atomic compare/swap)
> are now being used by the kernel, so parse these and stop the warnings
> when running make C=1 on current kernels.
> 
> WARNING: invalid argument to '-march': '_zacas_zabha'
> 
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>

Thanks Ben.  This saved me some time!

Tested-by: Paul Walmsley <pjw@kernel.org>


- Paul

  reply	other threads:[~2026-01-07 20:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-02 11:44 Two updates for RISC-V -march warnings Ben Dooks
2026-01-02 11:44 ` [PATCH 1/2] RISC-V: Stop warning about Zabha and Zacas Ben Dooks
2026-01-07 20:41   ` Paul Walmsley [this message]
2026-01-02 11:44 ` [PATCH 2/2] RISC-V: restart extension search on match Ben Dooks
2026-01-07 20:42   ` Paul Walmsley

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=c5021639-ca56-67cc-ccb5-e074e60bb19d@kernel.org \
    --to=pjw@kernel.org \
    --cc=ben.dooks@codethink.co.uk \
    --cc=linux-sparse@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox