All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charalampos Mitrodimas <charmitro@posteo.net>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Ruben Wauters <rubenru09@aol.com>,
	 Kernel Janitors List <kernel-janitors@vger.kernel.org>
Subject: Re: I have a pile of potential janitorial work for interested parties
Date: Mon, 30 Jun 2025 16:27:36 +0000	[thread overview]
Message-ID: <87sejhyz2f.fsf@posteo.net> (raw)
In-Reply-To: <84115bf4-bb53-3ebc-4076-5dae087fa4be@crashcourse.ca>

"Robert P. J. Day" <rpjday@crashcourse.ca> writes:

> On Mon, 30 Jun 2025, Ruben Wauters wrote:
>
> ... snip ...
>
>> Hello,
>>
>> Thank you for highlighting this, I believe this is a good target for
>> cleanup, and I would be interested in any other scripts you have
>> that provide similar information.
>>
>> I am fairly new to linux kernel development in general, not having a
>> large amount of patches to my name, however, opportunities for
>> cleanup and janitorial work, while often neglected by other
>> programmers for larger features, still are important in my opinion,
>> as it creates a more maintainable and cleaner codebase, as such I
>> would be very much interested in any cleanup opportunities.
>
> I started documenting these potential cleanups here:
>
> https://crashcourse.ca/doku/doku.php?id=linux_kernel_cleanup
>
> so anyone who's interested can start processing whatever parts of the
> kernel source tree that interests them.

Hi Robert,

This is going to be very helpful to newcomers that are looking forward
to contributing to the Linux kernel.

Looking at your list, the tools are awesome and well-thought. But I
believe some guidelines can be put in-place for some, so folks can get
their patches upstream easily, and of course, have some confidence in
it.

One guideline that came to mind almost immediately is regarding the
tools "Calculating the length of an array" is that people should pick a
subsystem and send a patchset, i.e. do not send a massive change that
changes code under more than one Kernel subsystem.

This approach respects maintainer, and simplifies the review process.

--
C. Mitrodimas

>
> There will be more cleanup scripts coming over the next few days.
>
> rday

  reply	other threads:[~2025-06-30 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-28 21:08 I have a pile of potential janitorial work for interested parties Robert P. J. Day
2025-06-30 14:42 ` Ruben Wauters
2025-06-30 15:15   ` Robert P. J. Day
2025-06-30 16:27     ` Charalampos Mitrodimas [this message]
2025-06-30 17:27       ` Robert P. J. Day

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=87sejhyz2f.fsf@posteo.net \
    --to=charmitro@posteo.net \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=rpjday@crashcourse.ca \
    --cc=rubenru09@aol.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.