public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Huang Shijie <b32955@freescale.com>
To: Huang Shijie <b32955@freescale.com>
Cc: <dwmw2@infradead.org>, <dedekind1@gmail.com>,
	<computersforpeace@gmail.com>, <linux-mtd@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/4] Export the ecc step size to user applications
Date: Thu, 8 Aug 2013 16:37:17 +0800	[thread overview]
Message-ID: <520358BD.6000808@freescale.com> (raw)
In-Reply-To: <1368607606-4344-1-git-send-email-b32955@freescale.com>

Hi Artem & Brian:
> In order to implement the NAND boot for some Freescale's chips, such as
> imx23/imx28/imx50/imx6, we use a tool (called kobs-ng) to burn the uboot
> and some metadata to nand chip. And the ROM code will use the metadata to
> configrate the BCH, and to find the uboot.
>
> The ECC information(ecc step size, ecc strength) which is used to configrate
> the BCH is part of the metadata. The kobs-ng can gets the ecc strength from
> the sys node /sys/*/mtdX/ecc_strength now. But it can't gets the ecc step size.
>
> This patch set is used to export the ecc step size to user applications.
> With this patch set, the kobs-ng can gets the ecc step size now.
>
> v1 --> v2:
> 	[1] rename the ecc_size to ecc_step.
> 	[2] rebase on the latest l2-mtd.
>
> Huang Shijie (4):
>   mtd: add a new field to mtd_info{}
>   mtd: add a new sys node to show the ecc step size
>   mtd: set the ecc step size for master/slave mtd_info
>   mtd: gpmi: update the ecc step size for mtd_info{}
>
>  drivers/mtd/mtdcore.c                  |   11 +++++++++++
>  drivers/mtd/mtdpart.c                  |    1 +
>  drivers/mtd/nand/gpmi-nand/gpmi-nand.c |    1 +
>  drivers/mtd/nand/nand_base.c           |    1 +
>  include/linux/mtd/mtd.h                |    3 +++
>  5 files changed, 17 insertions(+), 0 deletions(-)
>
Could you merge this patch set ?

thanks
Huang Shijie



      parent reply	other threads:[~2013-08-08  8:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15  8:46 [PATCH v2 0/4] Export the ecc step size to user applications Huang Shijie
2013-05-15  8:46 ` [PATCH v2 1/4] mtd: add a new field to mtd_info{} Huang Shijie
2013-05-15  8:46 ` [PATCH v2 2/4] mtd: add a new sys node to show the ecc step size Huang Shijie
2013-08-10  7:15   ` Brian Norris
2013-05-15  8:46 ` [PATCH v2 3/4] mtd: set the ecc step size for master/slave mtd_info Huang Shijie
2013-05-15  8:46 ` [PATCH v2 4/4] mtd: gpmi: update the ecc step size for mtd_info{} Huang Shijie
2013-08-10  7:41   ` Brian Norris
2013-08-10  7:53     ` Brian Norris
2013-08-11 15:07       ` Huang Shijie
2013-05-15 12:07 ` [PATCH v2 0/4] Export the ecc step size to user applications Artem Bityutskiy
2013-05-16  4:09   ` [PATCH v2 append] mtd: update the ABI document about the ecc step Huang Shijie
2013-08-10  8:20     ` Brian Norris
     [not found]   ` <CAMiH66GygmwvfZrwys7RoeoY4Q_fFkfbiZF_pJN4RxQBPaz0fw@mail.gmail.com>
2013-05-16  7:19     ` [PATCH v2 0/4] Export the ecc step size to user applications Artem Bityutskiy
2013-05-16  8:10       ` Huang Shijie
2013-08-08  8:37 ` Huang Shijie [this message]

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=520358BD.6000808@freescale.com \
    --to=b32955@freescale.com \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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