From: Will Deacon <will@kernel.org>
To: linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
linux-next@vger.kernel.org, u.kleine-koenig@pengutronix.de,
linux-perf-users@vger.kernel.org,
James Clark <james.clark@arm.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Nick Desaulniers <ndesaulniers@google.com>,
llvm@lists.linux.dev, Suzuki K Poulose <suzuki.poulose@arm.com>,
Bill Wendling <morbo@google.com>,
Justin Stitt <justinstitt@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/1] arm: perf: Fix ARCH=arm build with GCC
Date: Sun, 17 Dec 2023 13:41:05 +0000 [thread overview]
Message-ID: <170281440108.359132.7914631025593499836.b4-ty@kernel.org> (raw)
In-Reply-To: <20231215175648.3397170-1-james.clark@arm.com>
On Fri, 15 Dec 2023 17:56:47 +0000, James Clark wrote:
> Changes since V1:
>
> * Instead of wrapping everything in #if, just use GENMASK_ULL instead
> which fixes both issues in one commit.
>
> A fix for the broken build with GCC currently in linux-next
> (next-20231214)
>
> [...]
Applied to will (for-next/perf), thanks!
[1/1] arm: perf: Fix ARCH=arm build with GCC
https://git.kernel.org/will/c/bb339db4d363
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2023-12-17 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 17:56 [PATCH v2 0/1] arm: perf: Fix ARCH=arm build with GCC James Clark
2023-12-15 17:56 ` [PATCH v2 1/1] " James Clark
2023-12-15 18:20 ` Uwe Kleine-König
2023-12-16 12:44 ` Mark Rutland
2023-12-17 13:41 ` Will Deacon [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=170281440108.359132.7914631025593499836.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.clark@arm.com \
--cc=justinstitt@google.com \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mark.rutland@arm.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=suzuki.poulose@arm.com \
--cc=u.kleine-koenig@pengutronix.de \
/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