public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Linus Probert <linus.probert@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Status of kernel-janitors?
Date: Mon, 30 Mar 2026 14:10:49 +0200	[thread overview]
Message-ID: <acpeJQEPtDKQ68uo@mosquito> (raw)

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.

Br,
Linus Probert

             reply	other threads:[~2026-03-30 12:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 12:10 Linus Probert [this message]
2026-03-30 12:25 ` Status of kernel-janitors? Dan Carpenter
2026-03-30 12:51   ` Linus Probert

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=acpeJQEPtDKQ68uo@mosquito \
    --to=linus.probert@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    /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