public inbox for kernel-janitors@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: Kernel janitors website?
Date: Fri, 15 Feb 2013 08:40:18 +0000	[thread overview]
Message-ID: <20130215084018.GA6802@mwanda> (raw)
In-Reply-To: <87d2w2u5qv.fsf@steelpick.2x.cz>

On Thu, Feb 14, 2013 at 07:09:44PM +0100, Michal Sojka wrote:
> Hello,
> 
> we are running a university course [1] (in Czech) about working with
> open source communities. We try to help students with finding tasks and
> projects to work on. Do you have a web site listing the possible tasks
> for students?
> 
> It used to be http://janitor.kernelnewbies.org/ but it seems to be dead.
> Other pages http://kernelnewbies.org/KernelJanitors/Todo,
> https://code.google.com/p/kernel-janitors/wiki/TODO seem to be outdated.

Most of these still apply.

There is always stuff to fix in staging.  The thing about staging
though is that fixing style issues are fairly boring for students.
Also kernel style guidelines are very involved and we tend to be
stricter about pure style fixes than we are about bug fixes.

What I sometimes do is review short fixes and find similar bugs.

git checkout v3.3

git log --oneline v3.3-rc3..v3.3 | while read hash ; do
	if ! git show $hash | diffstat -l | grep -q "\.c$" ; then
		continue
	fi
	lines=$(git show $hash | diffstat | tail -n 1 | cut -d ' ' -f 5)
	echo $lines $hash
done | sort -n | cut -d ' ' -f 2 | tee hashes

for i in $(cat hashes) ; do
	git show $i
done | less

A lot of kernel janitor patches these days are static analysis
fixes.  I'm using Smatch.  A bunch of people are doing things with
Coccinelle.  I think Peter is using clang.  I think there are many
clang warnings left though.

I think as well, that you would find more warnings on non-x86
arches.

You could try asking for ideas on lkml.  We're always interested in
ideas as well.  Describe how long you'd want a typical project to
take.

regards,
dan carpenter

  reply	other threads:[~2013-02-15  8:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-14 18:09 Kernel janitors website? Michal Sojka
2013-02-15  8:40 ` Dan Carpenter [this message]
2013-02-15  8:50 ` Julia Lawall
2013-02-15  9:21 ` Dan Carpenter
2013-02-15  9:24 ` Julia Lawall
2013-02-15  9:29 ` Michal Sojka
2013-02-15 10:14 ` Dan Carpenter
2013-02-15 11:46 ` Dan Carpenter
2013-02-15 13:49 ` walter harms
2013-02-15 16:31 ` Michal Sojka

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=20130215084018.GA6802@mwanda \
    --to=dan.carpenter@oracle.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