[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <238beef1-16d3-4c72-ac7f-7d578ab8fc3d@linux.microsoft.com>
Date: Mon, 17 Mar 2025 10:28:38 -0700
From: Roman Kisel <romank@...ux.microsoft.com>
To: Arnd Bergmann <arnd@...db.de>
Cc: apais@...rosoft.com, benhill@...rosoft.com, bperkins@...rosoft.com,
sunilmut@...rosoft.com, bhelgaas@...gle.com, Borislav Petkov <bp@...en8.de>,
Catalin Marinas <catalin.marinas@....com>, Conor Dooley
<conor+dt@...nel.org>, Dan Carpenter <dan.carpenter@...aro.org>,
Dave Hansen <dave.hansen@...ux.intel.com>, Dexuan Cui <decui@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>, "H. Peter Anvin" <hpa@...or.com>,
Joey Gouly <joey.gouly@....com>, krzk+dt@...nel.org,
Krzysztof WilczyĆski <kw@...ux.com>,
"K. Y. Srinivasan" <kys@...rosoft.com>, Len Brown <lenb@...nel.org>,
Lorenzo Pieralisi <lpieralisi@...nel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@...aro.org>,
Mark Rutland <mark.rutland@....com>, Marc Zyngier <maz@...nel.org>,
Ingo Molnar <mingo@...hat.com>, Oliver Upton <oliver.upton@...ux.dev>,
"Rafael J . Wysocki" <rafael@...nel.org>, Rob Herring <robh@...nel.org>,
ssengar@...ux.microsoft.com, Sudeep Holla <sudeep.holla@....com>,
Suzuki K Poulose <suzuki.poulose@....com>,
Thomas Gleixner <tglx@...utronix.de>, Wei Liu <wei.liu@...nel.org>,
Will Deacon <will@...nel.org>, Zenghui Yu <yuzenghui@...wei.com>,
devicetree@...r.kernel.org, kvmarm@...ts.linux.dev,
linux-acpi@...r.kernel.org, Linux-Arch <linux-arch@...r.kernel.org>,
linux-arm-kernel@...ts.infradead.org, linux-hyperv@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH hyperv-next v6 01/11] arm64: kvm, smccc: Introduce and use
API for detecting hypervisor presence
On 3/15/2025 6:12 AM, Arnd Bergmann wrote:
> On Sat, Mar 15, 2025, at 01:27, Roman Kisel wrote:
>> On 3/14/2025 5:19 PM, Roman Kisel wrote:
>>
>> While the change is Acked, here is the caveat maybe.
>>
>> This patch produces warnings wtih sparse and CHECK_ENDING.
>> That said, the kernel build produces a whole lot more other warnings
>> from building with sparse by itself and/or with CHECK_ENDING.
>>
>> I am not sure how to proceed with that, thinking I should
>> not add warnings yet at the same time there are many others.
>> Not certain if folks take these signals as fyi or blockers.
>
> It would be best not to add warnigns. There is slow progress on
> fixing all the endianess warnings and I hope this can eventually
> complete, so even if there are many existing ones please try to
> keep new code clean.
>
Will fix the warnings, appreciate providing the guidance!
> Arnd
--
Thank you,
Roman
Powered by blists - more mailing lists