public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Steve Chen <schen@mvista.com>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"linux-arm-kernel@lists.arm.linux.org.uk"
	<linux-arm-kernel@lists.arm.linux.org.uk>,
	"Leo \(Hao\) Chen" <leochen@broadcom.com>
Subject: Re: [PATCH v3 26/27] [ARM] [NAND] [bcmring] add bcmring umi nand driver support
Date: Sun, 19 Jul 2009 05:56:24 -0500	[thread overview]
Message-ID: <1248000984.3079.130.camel@linux-1lbu> (raw)
In-Reply-To: <1247980139.11353.194.camel@localhost.localdomain>

On Sun, 2009-07-19 at 08:08 +0300, Artem Bityutskiy wrote:
> On Fri, 2009-07-17 at 12:13 -0700, Leo (Hao) Chen wrote:
> > This patch addes bcmring umi nand driver support, with bch ecc algorithm support.
> > 
> > It addes header files, register files, Kconfig option and Makefile
> > entry.
> > 
> > Signed-off-by: Leo Chen <leochen@broadcom.com>
> 
> Hi, the code neat in general, but would it be possible to amend it and
> make more compatible with the Linux coding style?
> 
> See Documentation/CodingStyle
> See scripts/checkpatch.pl
> 

Just to give an example of Artem's comment.  If I run the checkpatch
script on this patch, I get

> scripts/checkpatch.pl add_bcmring_umi_nand_driver_support.patch

WARNING: space prohibited between function name and open parenthesis '('
#157: FILE: arch/arm/mach-bcmring/include/mach/reg_nand.h:47:
+#define REG_NAND_DATA8          __REG8 (REG_NAND_PHYS_DATA8)

WARNING: line over 80 characters
#220: FILE: arch/arm/mach-bcmring/include/mach/reg_umi.h:38:
+#define HW_UMI_BASE       MM_IO_BASE_UMI       /* Unified Memory
Interface Ctrl Register */
...

ERROR: code indent should use tabs where possible
#1849: FILE: include/linux/mtd/nand_bcm_umi.h:227:
+               /* Flip bit */$

ERROR: code indent should use tabs where possible
#1850: FILE: include/linux/mtd/nand_bcm_umi.h:228:
+               nand_bcm_umi_bch_ecc_flip_bit(datap, errorLocation);$

total: 365 errors, 192 warnings, 1707 lines checked

add_bcmring_umi_nand_driver_support.patch has style problems, please
review.  If any of these errors are false positives report them to the
maintainer, see
CHECKPATCH in MAINTAINERS.

Regards,

Steve

  reply	other threads:[~2009-07-19 10:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-17 19:13 [PATCH v3 26/27] [ARM] [NAND] [bcmring] add bcmring umi nand driver support Leo (Hao) Chen
2009-07-19  5:08 ` Artem Bityutskiy
2009-07-19 10:56   ` Steve Chen [this message]
2009-07-21 22:46     ` Leo (Hao) Chen
2009-07-22  6:12       ` Artem Bityutskiy
2009-07-28 22:08   ` Leo (Hao) Chen
2009-07-28 22:38     ` Leo (Hao) Chen
2009-08-09  5:16       ` Artem Bityutskiy
2009-08-09  7:12         ` Scott Branden
2009-08-09  7:27           ` Artem Bityutskiy
2009-08-10 17:33             ` Scott Branden

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=1248000984.3079.130.camel@linux-1lbu \
    --to=schen@mvista.com \
    --cc=dedekind@infradead.org \
    --cc=leochen@broadcom.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-mtd@lists.infradead.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