linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Vlastimil Babka <vbabka@suse.cz>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: WangYuli <wangyuli@uniontech.com>,
	akpm@linux-foundation.org, Liam.Howlett@oracle.com,
	jannh@google.com, pfalcato@suse.de, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, niecheng1@uniontech.com,
	guanwentao@uniontech.com, Jun Zhan <zhanjun@uniontech.com>,
	linux-kbuild@vger.kernel.org
Subject: Re: [PATCH] tools/testing/vma: Fix function parameter declarations for GCC 8.3 compatibility
Date: Fri, 1 Aug 2025 11:22:14 +0200	[thread overview]
Message-ID: <6c81ed5c-32a6-4b4d-8468-770e0d375b00@suse.cz> (raw)
In-Reply-To: <27488afa-1d53-43eb-bc68-8e950d804000@lucifer.local>

On 8/1/25 10:50, Lorenzo Stoakes wrote:
> On Fri, Aug 01, 2025 at 10:04:11AM +0200, Vlastimil Babka wrote:
>>
>> Seems like newer gcc versions got more lenient. Haven't found why, but seems
>> they want it to stay like this:
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113825
>>
>> But I don't know if there's a way to make older gcc's lenient too.
>>
>> > I'll take another look.
>> >
>> > Thanks,
>> >
>>
> 
> WangYuli - apologies - this is my fault entirely, I misunderstood things
> here.
> 
> I was wrong to dismiss this out of hand, I guess not many headers are doing
> stubs like this, and I mistook this as being a general thing.
> 
> Could you please do a v2 where you add back in parameter names (and add
> this compiler flag - I think we still should),

It would be safer to add the compiler flag indeed, as we are including files
from mm/ in vma.c here, so if some change in mm/ files makes them rely on
syntax permitted only gnu11, we'd break the compilation of the test.

Also please update the commit log to talk about function definitions and not
function declarations, as that turned out to be the important detail. Thanks!



  reply	other threads:[~2025-08-01  9:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29  8:47 WangYuli
2025-07-29  9:06 ` Lorenzo Stoakes
2025-07-31  2:55   ` WangYuli
2025-07-31 10:24     ` Lorenzo Stoakes
2025-07-31 18:13       ` Vlastimil Babka
2025-08-01  5:14         ` Lorenzo Stoakes
2025-08-01  5:57           ` WangYuli
2025-08-01  8:04             ` Vlastimil Babka
2025-08-01  8:50               ` Lorenzo Stoakes
2025-08-01  9:22                 ` Vlastimil Babka [this message]
2025-08-01  9:26                 ` WangYuli
2025-08-01  9:33                   ` Lorenzo Stoakes
2025-08-01  9:48                     ` Vlastimil Babka

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=6c81ed5c-32a6-4b4d-8468-770e0d375b00@suse.cz \
    --to=vbabka@suse.cz \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=guanwentao@uniontech.com \
    --cc=jannh@google.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=niecheng1@uniontech.com \
    --cc=pfalcato@suse.de \
    --cc=wangyuli@uniontech.com \
    --cc=zhanjun@uniontech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox