From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: jmerkey@wolfmountaingroup.com
Cc: Masami Hiramatsu <mhiramat@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.27-rc1-git5 2/26] mdb: correct kprobes int3 trap
Date: Wed, 06 Aug 2008 10:15:27 +0200 [thread overview]
Message-ID: <48995D9F.4010900@s5r6.in-berlin.de> (raw)
In-Reply-To: <39379.166.70.238.45.1217950104.squirrel@webmail.wolfmountaingroup.com>
jmerkey@wolfmountaingroup.com wrote on 2008-08-05:
> I was unaware of checkpatch.pl, but will run it later today and submit a
> git6 patch for any areas not in compliance with linux coding standards.
I guess you got complaints from scripts/checkpatch.pl for at least 3/4
of all lines by now. Some or many of the complaints will probably look
silly. Have a look at Documentation/CodingStyle then because it gives
context for many of the complaints. It also gives some rules of thumb
for things which checkpatch.pl cannot check, e.g. legibility of global
names.
From what I saw, there are _many_ whitespace "deviations" in your code
(which perhaps scripts/Lindent can help to adjust), upper case vs. lower
case in names, and occasional functions which are deeper nested than
probably necessary, as already mentioned.
--
Stefan Richter
-=====-==--- =--- --==-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-08-06 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 6:26 [PATCH 2.6.27-rc1-git5 2/26] mdb: correct kprobes int3 trap jmerkey
2008-08-05 15:33 ` Masami Hiramatsu
2008-08-05 15:28 ` jmerkey
2008-08-06 8:15 ` Stefan Richter [this message]
[not found] ` <44714.166.70.238.45.1218029717.squirrel@webmail.wolfmountaingroup.com>
2008-08-06 16:32 ` Stefan Richter
2008-08-06 16:51 ` Masami Hiramatsu
2008-08-06 19:03 ` jmerkey
2008-08-06 8:40 ` Ananth N Mavinakayanahalli
2008-08-06 13:36 ` jmerkey
2008-08-06 12:21 ` Abhishek Sagar
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=48995D9F.4010900@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=jmerkey@wolfmountaingroup.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@redhat.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