From: Cyril Roelandt <tipecaml@gmail.com>
To: Alejandro del Rio <scasbyte@gmail.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Fix files with checkpatch errors/warnings
Date: Fri, 23 Dec 2011 02:33:04 +0100 [thread overview]
Message-ID: <4EF3DA50.80709@gmail.com> (raw)
In-Reply-To: <CAPbJ=BnAn6TfK9rFdVCSzcZizJOucUyJx0FfC03RYwH_zq-uJQ@mail.gmail.com>
On 12/22/2011 01:49 AM, Alejandro del Rio wrote:
> Hi all,
>
> I'm completely new to linux kernel development and I would like to
> make a very first contribution by "cleaning" some files. I noticed
> that the script checkpatch.pl (inside scripts/ folder) report lots of
> style errors on some drivers.
> For example try running ./scripts/checkpatch.pl --file
> drivers/video/*, you will notice that most of the files contain style
> issues.
>
> My questions are: Is people actively fixing this? Maybe they are not
> very interested on fixing this typos... Otherwise, could I contribute
> by submitting patches on this?
> And finally, if I do so, to who should I show this fixes?
Maybe you could help the Kernel Janitors :
http://kernelnewbies.org/KernelJanitors
http://vger.kernel.org/vger-lists.html#kernel-janitors
They "go through the linux kernel sources, doing code reviews, fixing up
unmaintained code and doing other cleanups and API conversion."
Cyril.
--
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2011-12-23 1:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAPbJ=B=KyJ4vM8iTT+K7xie3z13q5_7tj1mMqMAxXEh+XTQFXA@mail.gmail.com>
2011-12-22 0:49 ` Fix files with checkpatch errors/warnings Alejandro del Rio
2011-12-22 8:16 ` Anatoly Sivov
2011-12-22 16:56 ` Javier Martinez Canillas
2011-12-22 19:32 ` Anatoly Sivov
2011-12-23 1:33 ` Cyril Roelandt [this message]
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=4EF3DA50.80709@gmail.com \
--to=tipecaml@gmail.com \
--cc=linux-newbie@vger.kernel.org \
--cc=scasbyte@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).