From: Will Deacon <will@kernel.org>
To: "Sudip Mukherjee (Codethink)" <sudipm.mukherjee@gmail.com>
Cc: James Clark <james.clark@arm.com>,
Mark Brown <broonie@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-next@vger.kernel.org
Subject: Re: build failure of next-20220923 due to cbb0c02caf4b ("perf: arm64: Add SVE vector granule register to user regs")
Date: Fri, 23 Sep 2022 13:33:31 +0100 [thread overview]
Message-ID: <20220923123329.GA13942@willie-the-truck> (raw)
In-Reply-To: <Yy2braL3vc0SYDGl@debian>
On Fri, Sep 23, 2022 at 12:42:37PM +0100, Sudip Mukherjee (Codethink) wrote:
> Hi All,
>
> A native build of next-20220923 on arm64 host has failed with the error:
>
> ./usr/include/asm/perf_regs.h:42:26: error: C++ style comments are not allowed in ISO C90
> 42 | PERF_REG_ARM64_VG = 46, // SVE Vector Granule
> | ^
> ./usr/include/asm/perf_regs.h:42:26: note: (this will be reported only once per input file)
>
> I have not bisected but I think it will be from cbb0c02caf4b ("perf: arm64: Add SVE vector granule register to user regs").
>
> I will be happy to test any patch or provide any extra log if needed.
I had a crack at fixing this last night when it was first reported, so
hopefully the next -next will be alright.
Will
_______________________________________________
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:[~2022-09-23 12:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 11:42 build failure of next-20220923 due to cbb0c02caf4b ("perf: arm64: Add SVE vector granule register to user regs") Sudip Mukherjee (Codethink)
2022-09-23 12:33 ` 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=20220923123329.GA13942@willie-the-truck \
--to=will@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.clark@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.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;
as well as URLs for NNTP newsgroup(s).