public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <error27@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: Status of kernel-janitors?
Date: Mon, 30 Mar 2026 15:25:42 +0300	[thread overview]
Message-ID: <acprxrESPr1hnXkr@stanley.mountain> (raw)
In-Reply-To: <acpeJQEPtDKQ68uo@mosquito>

On Mon, Mar 30, 2026 at 02:10:49PM +0200, 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?
> 

Starting in driver/staging is good advice.

> 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.

Yeah.  After a while, you're left with only false positives or
we introduced new rules and the old code is sort of grandfathered
and the maintainers wouldn't appreciate an update.

> 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 tried to introduce the concept of, if you have an idea but don't
have the time to implement it right away, then write KTODO in your
email so people can search for that and get a list of ideas but it
hasn't really caught on.

regards,
dan carpenter

  reply	other threads:[~2026-03-30 12:25 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 [this message]
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
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=acprxrESPr1hnXkr@stanley.mountain \
    --to=error27@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