public inbox for sched-ext@lists.linux.dev
 help / color / mirror / Atom feed
From: Cheng-Yang Chou <yphbchou0911@gmail.com>
To: Andrea Righi <arighi@nvidia.com>
Cc: sched-ext@lists.linux.dev, tj@kernel.org, void@manifault.com,
	changwoo@igalia.com, jserv@ccns.ncku.edu.tw
Subject: Re: [PATCH] tools/sched_ext: Fix get_prandom_u64() prototype
Date: Sun, 8 Mar 2026 22:41:28 +0800	[thread overview]
Message-ID: <aa2KmIoXTq3PsPsJ@eric-acer> (raw)
In-Reply-To: <aa2BV-YMfe_NHFwV@gpd4>

On Sun, Mar 08, 2026 at 03:01:59PM +0100, Andrea Righi wrote:
> Hi,
> 
> On Sun, Mar 08, 2026 at 09:06:38PM +0800, Cheng-Yang Chou wrote:
> > In C99 (Sec 6.7.5.3), an empty parameter list in a declaration leaves
> > the parameter types unspecified (K&R style), not explicitly zero.
> > Consequently, the compiler would silently accept arbitrary arguments
> > passed to the function.
> > 
> > Declare the function with (void) to form a proper prototype asserting
> > it takes no arguments.
> > 
> > Signed-off-by: Cheng-Yang Chou <yphbchou0911@gmail.com>
> 
> I understand the motivation, but changes like this don't fix real issues or
> provide any measurable benefit. Patches consume maintainer and reviewer
> bandwidth, so it's usually best to focus on changes that fix real bugs or
> provide clear improvements.
> 
> If you encounter a real issue or can show a measurable improvement (with
> traces or numbers), patches addressing that would be much more useful.
> 
> Thanks,
> -Andrea

Understood.
Again, thanks for the explaination.

-- 
Thanks,
Cheng-Yang

      reply	other threads:[~2026-03-08 14:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-08 13:06 [PATCH] tools/sched_ext: Fix get_prandom_u64() prototype Cheng-Yang Chou
2026-03-08 14:01 ` Andrea Righi
2026-03-08 14:41   ` Cheng-Yang Chou [this message]

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=aa2KmIoXTq3PsPsJ@eric-acer \
    --to=yphbchou0911@gmail.com \
    --cc=arighi@nvidia.com \
    --cc=changwoo@igalia.com \
    --cc=jserv@ccns.ncku.edu.tw \
    --cc=sched-ext@lists.linux.dev \
    --cc=tj@kernel.org \
    --cc=void@manifault.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