public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Richard Weinberger <richard@nod.at>
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	dwmw2@infradead.org, computersforpeace@gmail.com
Subject: Re: [PATCH 1/3] mtd: nand: Add on-die ECC support
Date: Wed, 25 Mar 2015 21:39:05 +0100	[thread overview]
Message-ID: <1427315945.10958.48.camel@x220> (raw)
In-Reply-To: <1427292151-3835-2-git-send-email-richard@nod.at>

Probably not really the feedback you're hoping for at this moment, this
being an RFC, but I spotted two nits anyway.

On Wed, 2015-03-25 at 15:02 +0100, Richard Weinberger wrote:
> --- /dev/null
> +++ b/drivers/mtd/nand/nand_ondie.c

This file makes git am whine: "new blank line at EOF".

> +#include <linux/types.h>
> +#include <linux/kernel.h>
> +#include <linux/module.h>

Is this include needed? The code can only be built in. This files also
builds silently without that include. I used the rather hacky
    make EXTRA_CFLAGS="-DCONFIG_MTD_NAND_ECC_ON_DIE" drivers/mtd/nand/nand_ondie.o

to test the build.

> +#include <linux/slab.h>
> +#include <linux/bitops.h>
> +#include <linux/mtd/mtd.h>
> +#include <linux/mtd/nand.h>
> +#include <linux/mtd/nand_ondie.h>


Paul Bolle


  reply	other threads:[~2015-03-25 20:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 14:02 [RFC] On-die ECC support Richard Weinberger
2015-03-25 14:02 ` [PATCH 1/3] mtd: nand: Add on-die " Richard Weinberger
2015-03-25 20:39   ` Paul Bolle [this message]
2015-04-27 21:35   ` Ben Shelton
2015-04-27 22:19     ` Richard Weinberger
2015-04-27 22:36       ` Ben Shelton
2015-04-27 22:42         ` Richard Weinberger
2015-04-27 22:53           ` Brian Norris
2015-04-27 22:57             ` Richard Weinberger
2015-04-27 23:10               ` Brian Norris
2015-04-27 23:15                 ` Richard Weinberger
2015-04-27 23:19                   ` Brian Norris
2015-04-27 23:23       ` Brian Norris
2015-04-28  2:48         ` punnaiah choudary kalluri
2015-04-28  3:22           ` Brian Norris
2015-04-28  3:44             ` punnaiah choudary kalluri
2015-04-28 14:03               ` Josh Cartwright
2015-04-28 16:19                 ` punnaiah choudary kalluri
2015-05-08 21:26             ` Ben Shelton
2015-05-08 21:39               ` Brian Norris
2015-05-08 21:43                 ` Richard Weinberger
2015-04-28  3:15   ` punnaiah choudary kalluri
2015-03-25 14:02 ` [PATCH 2/3] mtd: nand: Add support for raw access when using on-die ECC Richard Weinberger
2015-03-25 14:02 ` [PATCH 3/3] mtd: nand: Wire up on-die ECC support Richard Weinberger
2015-04-21 12:31 ` [RFC] On-die " Richard Weinberger

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=1427315945.10958.48.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    /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