From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: TODO list
Date: Mon, 13 Apr 2015 22:02:34 +0000 [thread overview]
Message-ID: <20150413220234.GV16501@mwanda> (raw)
In-Reply-To: <20100714100136.GA3583@albatros>
On Mon, Apr 13, 2015 at 02:46:53PM -0700, Ravi Kerur wrote:
> Team,
>
> I will take up net/sched files and get a clean checkpatch run on them. I am working on a project which involves this piece of code and as part of learning the code I can clean-up the files. I ran checkpatch on some of them and I do see that it needs cleaning. For e.g.
>
> #:~/git/kernels/staging$ perl scripts/checkpatch.pl -f net/sched/act_api.c
> WARNING: networking block comments don't use an empty /* line, use /* Comment...
> #41: FILE: net/sched/act_api.c:41:
> + /*
> + * gen_estimator est_timer() might access p->tcfc_locki
>
> CHECK: Comparison to NULL could be written "!nest"
> #95: FILE: net/sched/act_api.c:95:
> + if (nest = NULL)
> ...
> [...]
No one cares about either of those things. If it's a drivers/staging
patch then we would merge it, but if it's a patch to net/sched/act_api.c
they will probably just get annoyed with you.
regards,
dan carpenter
next prev parent reply other threads:[~2015-04-13 22:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 10:01 TODO list Kulikov Vasiliy
2012-07-08 13:38 ` TODO List Benjamin BEURDOUCHE
2012-07-09 0:51 ` Keith Woodie
2015-04-03 20:40 ` TODO list Ravi Kerur
2015-04-07 7:49 ` Dan Carpenter
2015-04-09 0:36 ` Ravi Kerur
2015-04-09 8:48 ` Dan Carpenter
2015-04-09 22:57 ` Ravi Kerur
2015-04-10 5:34 ` Julia Lawall
2015-04-10 22:47 ` Ravi Kerur
2015-04-11 5:17 ` Julia Lawall
2015-04-13 22:02 ` Dan Carpenter [this message]
2015-04-13 22:42 ` Ravi Kerur
2015-04-14 6:58 ` Dan Carpenter
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=20150413220234.GV16501@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;
as well as URLs for NNTP newsgroup(s).