[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <37b606a7-17c6-4865-a78a-ddde1bc15649@lucifer.local>
Date: Thu, 31 Jul 2025 11:24:18 +0100
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: WangYuli <wangyuli@...ontech.com>
Cc: akpm@...ux-foundation.org, Liam.Howlett@...cle.com, vbabka@...e.cz,
jannh@...gle.com, pfalcato@...e.de, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, niecheng1@...ontech.com,
guanwentao@...ontech.com, Jun Zhan <zhanjun@...ontech.com>,
linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] tools/testing/vma: Fix function parameter declarations
for GCC 8.3 compatibility
On Thu, Jul 31, 2025 at 10:55:32AM +0800, WangYuli wrote:
> >
> Thanks for the heads-up! I noticed that coding style in the kernel code as
> well.
>
> However, GCC 8.3 (which does meet the kernel's compiler version
> requirements) can compile the kernel code normally, but it can't compile
> vma's test correctly.
>
> Could the issue be related to differences in compilation parameters? I'll
> need to spend some time looking into this more closely...
OK thanks please do check, am happy to have a patch to add a flag if
appropriate! :)
>
> By the way, this coding style has been a GNU C extension until the ISO C23
> standard. So, until the kernel's C language standard is upgraded to C23
> (which seems unlikely to happen anytime soon, perhaps years down the line),
> it actually makes sense to modify this style for a practical purpose...
Kernel always uses the GNU C standard by convention, so we should be good,
but indeed I think this is the case!
The irony here is that I actually intend to change stubs in this header to
remove parameter names (previously had review on this :).
>
> [ Cc the kbuild list. ]
Thanks
>
> Thanks,
>
> --
> WangYuli
Cheers, Lorenzo
Powered by blists - more mailing lists