All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Richard Weinberger <richard@nod.at>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PULL] mtd: nand: changes for 4.7
Date: Thu, 5 May 2016 11:38:15 -0700	[thread overview]
Message-ID: <20160505183815.GA89390@google.com> (raw)
In-Reply-To: <20160429101348.309d4784@bbrezillon>

Hi Boris,

On Fri, Apr 29, 2016 at 10:13:48AM +0200, Boris Brezillon wrote:
> Hi Brian,
> 
> This is my first PR for the NAND subsystem, so don't hesitate to tell me
> if I did something wrong ;).

Overall things aren't too bad, but I do have some comments.

> This pull request contains the following infrastructure changes:
> * introduction of the ECC algo concept to extend the ECC mode one
> * replacement of the nand_ecclayout infrastructure by something more
>   future-proof.
> * addition of an mtd-activity led trigger to replace the nand-activity
>   one
> 
> And a bunch of specific NAND driver improvements/fixes. Here are the
> changes that are worth mentioning:
> * rework of the OMAP GPMC and NAND drivers
> * prepare the sunxi NAND driver to receive DMA support
> * handle bitflips in erased pages on GPMI revisions that do not support
>   this in hardware.

Thanks for the summary; it'd be nice if you can include this in the tag
description next time. Then it'll get auto-populated below with
git-request-pull, and it'll get pulled in automatically for me.

I also see this when I try to build a reasonably simple kernel:

depmod: ERROR: Found 5 modules in dependency cycles!
depmod: ERROR: Cycle detected: nand -> nand_bch -> nand

I think the new reference to &nand_ooblayout_lp_ops in nand_bch.c is
causing this (I can at least build/boot if I hack that out).

I haven't finished looking through everything else, but mostly looks
sane.

Regards,
Brian

> Best Regards,
> 
> Boris
> 
> The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:
> 
>   Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)
> 
> are available in the git repository at:
> 
>   git@github.com:linux-nand/linux.git tags/nand/for-4.7
> 
> for you to fetch changes up to 4ab41e74ae5df89b8bc9909ba35fc19bbd1d6221:
> 
>   mtd: brcmnand: respect ECC algorithm set by NAND subsystem (2016-04-27 09:51:43 +0200)
> 
> ----------------------------------------------------------------
> This tag contains all the NAND related changes for 4.7.
> 
> ----------------------------------------------------------------

[snip]

  reply	other threads:[~2016-05-05 18:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29  8:13 [PULL] mtd: nand: changes for 4.7 Boris Brezillon
2016-05-05 18:38 ` Brian Norris [this message]
2016-05-06  7:01   ` Boris Brezillon

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=20160505183815.GA89390@google.com \
    --to=computersforpeace@gmail.com \
    --cc=boris.brezillon@free-electrons.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.