From: Marc Zyngier <maz@kernel.org>
To: Sebastian Ott <sebott@redhat.com>
Cc: linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org,
Oliver Upton <oliver.upton@linux.dev>,
James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Zenghui Yu <yuzenghui@huawei.com>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v2 0/3] KVM: arm64: fix warnings in W=1 build
Date: Tue, 23 Jul 2024 18:04:34 +0100 [thread overview]
Message-ID: <86cyn42g65.wl-maz@kernel.org> (raw)
In-Reply-To: <20240723101204.7356-1-sebott@redhat.com>
On Tue, 23 Jul 2024 11:12:01 +0100,
Sebastian Ott <sebott@redhat.com> wrote:
>
> Building arch/arm64/kvm/ with W=1 spills out a lot of warnings. When
> changing stuff I try to use as much tooling as possible to make sure
> that I don't screw up - having a clean baseline imho helps with that.
>
> With the first 2 patches applied make W=1 arch/arm64/kvm/ runs without
> warnings for me (fedora userspace, upstream linux after kvm merge).
> Patch 3 gets rid of sparse lock warnings in arch/arm64/kvm/vgic/.
>
> Patch 1 now just adds -Wno-override-init to the cflags of the affected
> files. Alternatives would be to add this to the whole subdir or
> reintroduce the flag for higher warn levels..
>
> Sebastian Ott (3):
> KVM: arm64: fix override-init warnings in W=1 builds
> KVM: arm64: fix kdoc warnings in W=1 builds
> KVM: arm64: vgic: fix unexpected unlock sparse warnings
>
> arch/arm64/kvm/Makefile | 3 +++
> arch/arm64/kvm/arm.c | 1 +
> arch/arm64/kvm/hyp/nvhe/Makefile | 2 ++
> arch/arm64/kvm/hyp/vhe/Makefile | 2 ++
> arch/arm64/kvm/vgic/vgic-irqfd.c | 7 ++++---
> arch/arm64/kvm/vgic/vgic-its.c | 18 +++++++++++-------
> arch/arm64/kvm/vgic/vgic-v3.c | 2 +-
> arch/arm64/kvm/vgic/vgic.c | 2 +-
> arch/arm64/kvm/vgic/vgic.h | 2 +-
> 9 files changed, 26 insertions(+), 13 deletions(-)
For the series, and assuming we take this in 6.11::
Reviewed-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-07-23 17:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-23 10:12 [PATCH v2 0/3] KVM: arm64: fix warnings in W=1 build Sebastian Ott
2024-07-23 10:12 ` [PATCH v2 1/3] KVM: arm64: fix override-init warnings in W=1 builds Sebastian Ott
2024-07-23 10:12 ` [PATCH v2 2/3] KVM: arm64: fix kdoc " Sebastian Ott
2024-07-23 10:12 ` [PATCH v2 3/3] KVM: arm64: vgic: fix unexpected unlock sparse warnings Sebastian Ott
2024-07-23 17:04 ` Marc Zyngier [this message]
2024-08-05 22:12 ` [PATCH v2 0/3] KVM: arm64: fix warnings in W=1 build Oliver Upton
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=86cyn42g65.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=oliver.upton@linux.dev \
--cc=sebott@redhat.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.