From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: linux-stable <stable@vger.kernel.org>,
lkft-triage@lists.linaro.org, Sasha Levin <sashal@kernel.org>,
Marc Zyngier <maz@kernel.org>, Reiji Watanabe <reijiw@google.com>,
Oliver Upton <oliver.upton@linux.dev>
Subject: Re: stable-rc / queue : 5.15: arm64 build failed
Date: Tue, 11 Apr 2023 16:03:41 +0200 [thread overview]
Message-ID: <2023041129-booting-uncorrupt-3457@gregkh> (raw)
In-Reply-To: <CA+G9fYs7nv16aP9q2Y7sgYAXMEwbnkYmzs7o21wRHGZRRrv=4g@mail.gmail.com>
On Tue, Apr 11, 2023 at 07:26:41PM +0530, Naresh Kamboju wrote:
> Hi,
>
> On Mon, 3 Apr 2023 at 18:35, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > On Mon, Apr 03, 2023 at 03:47:11PM +0530, Naresh Kamboju wrote:
> > > Following build warning noticed on arm64,
> > >
> > > Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
> > >
>
> This patch is now in queue 5.15,
>
> > > suspecting commit:
> > > KVM: arm64: PMU: Fix GET_ONE_REG for vPMC regs to return the current value
> > > commit 9228b26194d1cc00449f12f306f53ef2e234a55b upstream.
> >
> > Now dropped, thanks!
>
> I have started noticing this build error again on queue 5.15.
>
> arch/arm64/kvm/sys_regs.c:1671:43: error: initialization of 'int
> (*)(struct kvm_vcpu *, const struct sys_reg_desc *, const struct
> kvm_one_reg *, void *)' from incompatible pointer type 'int (*)(struct
> kvm_vcpu *, const struct sys_reg_desc *, u64 *)' {aka 'int (*)(struct
> kvm_vcpu *, const struct sys_reg_desc *, long long unsigned int *)'}
> [-Werror=incompatible-pointer-types]
> 1671 | .reg = PMCCNTR_EL0, .get_user = get_pmu_evcntr},
> | ^~~~~~~~~~~~~~
> arch/arm64/kvm/sys_regs.c:1671:43: note: (near initialization for
> 'sys_reg_descs[224].__get_user')
> arch/arm64/kvm/sys_regs.c:999:48: error: initialization of 'int
> (*)(struct kvm_vcpu *, const struct sys_reg_desc *, const struct
> kvm_one_reg *, void *)' from incompatible pointer type 'int (*)(struct
> kvm_vcpu *, const struct sys_reg_desc *, u64 *)' {aka 'int (*)(struct
> kvm_vcpu *, const struct sys_reg_desc *, long long unsigned int *)'}
> [-Werror=incompatible-pointer-types]
> 999 | .reset = reset_pmevcntr, .get_user = get_pmu_evcntr,
> \
> | ^~~~
>
>
> https://qa-reports.linaro.org/lkft/linux-stable-rc-queues-queue_5.15/build/v5.15.105-187-ga996798ba4fa/testrun/16173915/suite/build/test/gcc-11-defconfig-lkftconfig/history/
Thanks, I've dropped it from the queue now.
greg k-h
prev parent reply other threads:[~2023-04-11 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 10:17 stable-rc / queue : 5.15: arm64 build failed Naresh Kamboju
2023-04-03 13:05 ` Greg Kroah-Hartman
2023-04-11 13:56 ` Naresh Kamboju
2023-04-11 14:03 ` Greg Kroah-Hartman [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=2023041129-booting-uncorrupt-3457@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=lkft-triage@lists.linaro.org \
--cc=maz@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=oliver.upton@linux.dev \
--cc=reijiw@google.com \
--cc=sashal@kernel.org \
--cc=stable@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