Contributing via kernel-janitors

Contributing via kernel-janitors

[Dr. George E. Moore]

I'm unclear as to how via kernel-janitors, I can support patches to the
kernel. Are bug/documentation anomalies already identified in some
archive, or are we expected to choose a subsystem, search for such
anomalies as described in the KernelJanitor/Todo page, acknowledge our
willingness to make fixes and submit patches to
kernel-janitors at vgerkernel.org? What kernel subsystems are current being
reviewed and patched by kernel-janitors?

I'm certainly willing to lend my support to this work; hwever, I could
use some guidance.

Contributing via kernel-janitors

[Valdis.Kletnieks at vt.edu]

On Wed, 14 Jan 2015 11:07:22 -0500, "Dr. George E. Moore" said:
> I'm unclear as to how via kernel-janitors, I can support patches to the
> kernel. Are bug/documentation anomalies already identified in some
> archive, or are we expected to choose a subsystem, search for such
> anomalies as described in the KernelJanitor/Todo page, acknowledge our
> willingness to make fixes and submit patches to
> kernel-janitors at vgerkernel.org? What kernel subsystems are current being
> reviewed and patched by kernel-janitors?

Pretty much none.

At one time, people would add new/changed APIs to the kernel, and
kernel-janitors would go around and fix the usage to match the new API.
However, a number of years ago, we started requiring that patch sets that
change an API also include patches to change all the users, so there's a lot
less cleanup work of that sort to do.

However, if you're wanting to get your feet wet, there's a *lot* of really
bad code in drivers/staging/ that needs a lot of care before it can move
to the main part of the kernel tree.  Everything under drivers/staging/
should have its own TODO file listing things that are *known* to need fixing
in the driver - and there's probably a half-ton of bad coding in the driver
that isn't listed in the TODO.  Greg KH is *always* looking for people
to dive in and provide patches. :)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 848 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20150115/35acd6f7/attachment.bin 

Contributing via kernel-janitors

[Silvan Jegen]

Hi

Am 2015-01-14 17:07, schrieb Dr. George E. Moore:
> I'm certainly willing to lend my support to this work; hwever, I could
> use some guidance.

Another way to contribute is to run the smatch C static code analyzer 
tool on the Kernel which you can find here

http://smatch.sourceforge.net/

There are thousands of issues being reported (of which quite a lot are 
false positives, mind you).


Cheers,

Silvan

Contributing via kernel-janitors

[Greg Donald]

On Wed, Jan 14, 2015 at 10:07 AM, Dr. George E. Moore <gem@x-ctr-l.com> wrote:
> I'm certainly willing to lend my support to this work; hwever, I could
> use some guidance.

I watched this a few times to learn how to submit my first patch:

https://www.youtube.com/watch?v=LLBrBBImJt4


-- 
Greg Donald