From: Joe Perches <joe@perches.com>
To: "\"Levan Giguashvili" <levangig@gmail.com>
Cc: rusty@rustcorp.com.au, mingo@kernel.org, jim.cromie@gmail.com,
viro@zeniv.linux.org.uk, hpa@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] init: main: fixed coding style issues and errors
Date: Mon, 15 Oct 2012 04:48:57 -0700 [thread overview]
Message-ID: <1350301737.6851.9.camel@joe-AO722> (raw)
In-Reply-To: <1350290504-13931-1-git-send-email-user@ubuntu>
On Mon, 2012-10-15 at 10:41 +0200, "Levan Giguashvili wrote:
> From: Odinn <odinn@ubuntu.(none)>
who's that? Make sure your from line is correct please.
> Fixed coding style issues regarding spaces and braces.
> Removed init of a static variable.
> Added KERN_DEBUG to printk that was missing it
Added unnecessary continuation lines to printks.
> diff --git a/init/main.c b/init/main.c
[]
> @@ -172,8 +172,8 @@ static int __init obsolete_checksetup(char *line)
> if (line[n] == '\0' || line[n] == '=')
> had_early_param = 1;
> } else if (!p->setup_func) {
> - printk(KERN_WARNING "Parameter %s is obsolete,"
> - " ignored\n", p->str);
> + printk(KERN_WARNING "Parameter %s is obsolete" \
> + ", ignored\n", p->str);
Don't add unnecessary line continuations please.
Better would be to coalesce the formats like:
printk(KERN_WARNING "Parameter %s is obsolete, ignored\n"
p->str);
It would also be better and easier to review if you
broke out the whitespace only changes as a separate
patch from the other changes you make.
Oh, and please make these sorts of changes only in
the drivers/staging tree until you are _very_ familiar
with kernel style. Don't rely on checkpatch to tell
you what to do. It's pretty brain-dead. checkpatch
is a patch checking tool not really a code style tool
for existing code.
prev parent reply other threads:[~2012-10-15 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-15 8:41 "Levan Giguashvili
2012-10-15 11:48 ` Joe Perches [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=1350301737.6851.9.camel@joe-AO722 \
--to=joe@perches.com \
--cc=hpa@linux.intel.com \
--cc=jim.cromie@gmail.com \
--cc=levangig@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®