[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9a7681c3-f09e-8b8d-35d7-051268ce6d54@arm.com>
Date: Tue, 4 Jun 2019 10:01:25 +0100
From: Marc Zyngier <marc.zyngier@....com>
To: Catalin Marinas <catalin.marinas@....com>,
Viresh Kumar <viresh.kumar@...aro.org>
Cc: Dave Martin <Dave.Martin@....com>,
James Morse <james.morse@....com>,
Julien Thierry <julien.thierry@....com>,
Suzuki K Pouloze <suzuki.poulose@....com>,
Will Deacon <will.deacon@....com>,
Vincent Guittot <vincent.guittot@...aro.org>,
linux-arm-kernel@...ts.infradead.org, kvmarm@...ts.cs.columbia.edu,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] KVM: arm64: Drop 'const' from argument of vq_present()
On 04/06/2019 09:43, Catalin Marinas wrote:
> On Tue, Jun 04, 2019 at 10:13:19AM +0530, Viresh Kumar wrote:
>> We currently get following compilation warning:
>>
>> arch/arm64/kvm/guest.c: In function 'set_sve_vls':
>> arch/arm64/kvm/guest.c:262:18: warning: passing argument 1 of 'vq_present' from incompatible pointer type
>> arch/arm64/kvm/guest.c:212:13: note: expected 'const u64 (* const)[8]' but argument is of type 'u64 (*)[8]'
>
> Since the vq_present() function does not modify the vqs array, I don't
> understand why this warning. Compiler bug?
Yeah, I'm a bit puzzled by that one. Also checked with clang, which is
usually much more picky about things, but it didn't complain.
We could drop the const without much harm, but I really wish we weed out
these ancient compilers...
Thanks,
M.
--
Jazz is not dead. It just smells funny...
Powered by blists - more mailing lists