From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-riscv@lists.infradead.org, Conor Dooley <conor@kernel.org>
Cc: Will Deacon <will@kernel.org>,
Conor Dooley <conor.dooley@microchip.com>,
Palmer Dabbelt <palmer@rivosinc.com>,
Mark Rutland <mark.rutland@arm.com>,
Ji Sheng Teoh <jisheng.teoh@starfivetech.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] perf: starfive: fix 64-bit only COMPILE_TEST condition
Date: Tue, 19 Mar 2024 19:04:40 +0000 [thread overview]
Message-ID: <171087507362.45404.9535094447088311477.b4-ty@arm.com> (raw)
In-Reply-To: <20240318-emphatic-rally-f177a4fe1bdc@spud>
On Mon, 18 Mar 2024 15:35:04 +0000, Conor Dooley wrote:
> ARCH_STARFIVE is not restricted to 64-bit platforms, so while Will's
> addition of a 64-bit only condition satisfied the build robots doing
> COMPILE_TEST builds, Palmer ran into the same problems with writeq()
> being undefined during regular rv32 builds.
>
> Promote the dependency on 64-bit to its own `depends on` so that the
> driver can never be included in 32-bit builds.
>
> [...]
Applied to arm64 (for-next/core), thanks!
[1/1] perf: starfive: fix 64-bit only COMPILE_TEST condition
https://git.kernel.org/arm64/c/1d63d1d9e5c5
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2024-03-19 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 15:35 [PATCH v1] perf: starfive: fix 64-bit only COMPILE_TEST condition Conor Dooley
2024-03-18 16:15 ` Palmer Dabbelt
2024-03-18 16:25 ` JiSheng Teoh
2024-03-18 17:12 ` Emil Renner Berthing
2024-03-19 15:56 ` Will Deacon
2024-03-19 16:12 ` Conor Dooley
2024-03-19 19:04 ` Catalin Marinas [this message]
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=171087507362.45404.9535094447088311477.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=jisheng.teoh@starfivetech.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=palmer@rivosinc.com \
--cc=will@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