public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: "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: Mon, 30 Mar 2026 23:48:50 +0300	[thread overview]
Message-ID: <acrhsqvXp4R-egW4@stanley.mountain> (raw)
In-Reply-To: <e25aa771-d3d2-4b93-31b8-15576e1d9512@crashcourse.ca>

On Mon, Mar 30, 2026 at 09:27:25AM -0400, Robert P. J. Day wrote:
> On Mon, 30 Mar 2026, Linus Probert wrote:
> 
> > Hello,
> >
> > I've been a long time builder and fiddler of kernel source. Running
> > self-compiled kernels and pulling in patches before official release
> > etc. Bog standard for most of you I assume.
> >
> > I'd love to dedicate some spare to help the project. Like so many
> > others.
> >
> > The kernel-janoitors "project" does pop up in various resources such as
> > kernelnewbies and I think it might have been mentioned in one of the
> > Linux Foundations free courses. But links to potential homepages seem to
> > be dead and resources are sometimes dated.
> >
> > I read somewhere that this has mostly evolved into janitorial work in
> > drivers/staging. TODOs were mentioned.
> >
> > So the actual question. In my mind janitorial code work is a good place
> > to dip ones toes when starting out. Is this the right mailing list to
> > ask about such things? Any suggestions to find an area where ones
> > assistance would be welcome?
> >
> > I'm aware of checkpatch.pl but for many drivers diverging from these
> > rules seem intentional and just blindly fixing checkpatch warnings are
> > not helpful to the maintainer.
> > Open source is a lot of work so the goal would be to be helpful while
> > not stealing too much attention from concerned parties.
> 
>   I mention this once in a while ... *many* years ago, I wrote some
> admittedly hacky scripts that scanned the kernel source tree looking
> for what I considered "obvious" cleanups. One of those cleanups was to
> abbreviate the numerous calculations of the length of an array
> sprinkled throughout the source code,

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

regards,
dan carpenter


  parent reply	other threads:[~2026-03-30 20:48 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 [this message]
2026-03-30 21:09     ` Robert P. J. Day
2026-04-02 21:57     ` Linus Probert
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=acrhsqvXp4R-egW4@stanley.mountain \
    --to=error27@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linus.probert@gmail.com \
    --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