From: Lee Jones <lee.jones@linaro.org>
To: Pekon Gupta <pekon@TI.COM>
Cc: Brian Norris <computersforpeace@gmail.com>,
avinashphilipk@gmail.com, Felipe Balbi <balbi@TI.COM>,
linux-mtd <linux-mtd@lists.infradead.org>,
Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
Stefan Roese <sr@denx.de>
Subject: Re: [PATCH v6 0/4] mtd: devices: elm: add checks ELM H/W constrains, driver code cleanup
Date: Tue, 11 Mar 2014 10:14:12 +0000 [thread overview]
Message-ID: <20140311101342.GA18811@lee--X1> (raw)
In-Reply-To: <1394197344-9468-1-git-send-email-pekon@ti.com>
> *changes v5 -> v6*
> [PATCH 02/04] minor cleanup
>
> *changes v4 -> v5*
> This patch series is split version from earlier series [1].
> This series refactors and cleans ELM driver which is used by Hardware
> based BCHx ecc-schemes.
> - Undo: introduction of 'struct mtd_info' and 'struct nand_chip'. Instead
> keep ELM driver independent of mtd_info and nand_chip structs and
> pass only required ECC configurations as elm_config() arguments
> elm_config(..., int ecc_steps, int ecc_step_size, int ecc_step_bytes)
> - Undo: re-writing of elm_load_syndrome() ECC register configurations.
>
> *changes v3 -> v4 [1]*
> - in-corporated feedbacks from Brian Norris <computersforpeace@gmail.com>
> - updated: use 'pr_fmt(fmt)' to suffix DRIVER_NAME
> - removed: local 'eccsteps' in ELM driver, instead using nand_chip->ecc.steps
> - undo: irrelavant white-space changes
>
> [1] http://lists.infradead.org/pipermail/linux-mtd/2013-November/050242.html
>
> Pekon Gupta (4):
> mtd: devices: elm: check for hardware engine's design constrains
> mtd: devices: elm: clean elm_load_syndrome
> mtd: devices: elm: configure parallel channels based on ecc_steps
> mtd: devices: elm: update DRIVER_NAME as "omap-elm"
>
> drivers/mtd/devices/elm.c | 44 +++++++++++++++++++++++++++++----------
> drivers/mtd/nand/omap2.c | 9 +++++---
> include/linux/platform_data/elm.h | 10 ++-------
> 3 files changed, 41 insertions(+), 22 deletions(-)
I can't seem to be able to apply this set. What kernel release it is
based on?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-03-11 10:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-07 13:02 [PATCH v6 0/4] mtd: devices: elm: add checks ELM H/W constrains, driver code cleanup Pekon Gupta
2014-03-07 13:02 ` [PATCH v6 1/4] mtd: devices: elm: check for hardware engine's design constrains Pekon Gupta
2014-03-10 13:35 ` Ezequiel Garcia
2014-03-12 11:08 ` Gupta, Pekon
2014-03-07 13:02 ` [PATCH v6 2/4] mtd: devices: elm: clean elm_load_syndrome Pekon Gupta
2014-03-07 13:02 ` [PATCH v6 3/4] mtd: devices: elm: configure parallel channels based on ecc_steps Pekon Gupta
2014-03-10 14:08 ` Ezequiel Garcia
2014-03-07 13:02 ` [PATCH v6 4/4] mtd: devices: elm: update DRIVER_NAME as "omap-elm" Pekon Gupta
2014-03-10 13:59 ` Ezequiel Garcia
2014-03-11 10:14 ` Lee Jones [this message]
2014-03-11 10:18 ` [PATCH v6 0/4] mtd: devices: elm: add checks ELM H/W constrains, driver code cleanup Gupta, Pekon
2014-03-11 11:47 ` Lee Jones
2014-03-11 11:57 ` Gupta, Pekon
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=20140311101342.GA18811@lee--X1 \
--to=lee.jones@linaro.org \
--cc=avinashphilipk@gmail.com \
--cc=balbi@TI.COM \
--cc=computersforpeace@gmail.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-mtd@lists.infradead.org \
--cc=pekon@TI.COM \
--cc=sr@denx.de \
/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.