From: "Linus Probert" <linus.probert@gmail.com>
To: "Dan Carpenter" <error27@gmail.com>,
"Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "Linus Probert" <linus.probert@gmail.com>,
<kernel-janitors@vger.kernel.org>
Subject: Re: Status of kernel-janitors?
Date: Thu, 02 Apr 2026 23:57:21 +0200 [thread overview]
Message-ID: <DHJ074MZJ7KP.300Y06YAUW7IX@gmail.com> (raw)
In-Reply-To: <acrhsqvXp4R-egW4@stanley.mountain>
On Mon Mar 30, 2026 at 10:48 PM CEST, Dan Carpenter wrote:
> On Mon, Mar 30, 2026 at 09:27:25AM -0400, Robert P. J. Day wrote:
>> On Mon, 30 Mar 2026, Linus Probert wrote:
[...]
> There is a coccinelle check for this already. I don't know why it
> hasn't been done to NUM_ELEMENTS().
>
> scripts/coccinelle/misc/array_size.cocci
So. I have patches for the amd gpu which I can submit. Just not sure if
these have been left out for a reason or if the coccinelle check just
missed these.
I'm also not 100% sure where I send them. I made the changes on my local
staging-testing clone/branch. But these drivers are not in staging. Do
they still go through the same channels?
This is the gist of it:
- drm/amd/display: Remove unused NUM_ELEMENTS macros
- drm/amd/display: Replace inline NUM_ELEMENTS macro with ARRAY_SIZE
Some guidance on this would be most welcome.
Br,
Linus
next prev parent reply other threads:[~2026-04-02 21:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-30 12:10 Status of kernel-janitors? Linus Probert
2026-03-30 12:25 ` Dan Carpenter
2026-03-30 12:51 ` Linus Probert
2026-03-30 13:27 ` Robert P. J. Day
2026-03-30 20:32 ` Linus Probert
2026-03-30 20:48 ` Dan Carpenter
2026-03-30 21:09 ` Robert P. J. Day
2026-04-02 21:57 ` Linus Probert [this message]
2026-04-03 0:01 ` Julia Lawall
2026-04-03 21:12 ` Linus Probert
2026-04-03 22:20 ` Rolf Reintjes
2026-04-03 22:26 ` Linus Probert
2026-04-04 16:29 ` Ethan Tidmore
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=DHJ074MZJ7KP.300Y06YAUW7IX@gmail.com \
--to=linus.probert@gmail.com \
--cc=error27@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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