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: Han Xu <xhnjupt@gmail.com>, Huang Shijie <shijie.huang@arm.com>,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH] remove deprecated oobinfo retrieval
Date: Tue, 26 Jan 2016 11:59:41 -0800	[thread overview]
Message-ID: <20160126195941.GA118766@google.com> (raw)
In-Reply-To: <1453790537-20566-1-git-send-email-boris.brezillon@free-electrons.com>

On Tue, Jan 26, 2016 at 07:42:16AM +0100, Boris Brezillon wrote:
> From: Boris BREZILLON <boris.brezillon@free-electrons.com>
> 
> This remove OOB info retrieval, which is not used anywhere else in the code
> and can generate errors when called on newer NAND that have more than 32
> bytes of ECC or 16 bytes available for user usage in the OOB area.
> 
> Signed-off-by: Boris BREZILLON <boris.brezillon@free-electrons.com>
> ---
>  src/mtd.c | 8 --------
>  src/mtd.h | 1 -
>  2 files changed, 9 deletions(-)

What source are you trying to patch? Doesn't look like Linux or
mtd-utils.

  parent reply	other threads:[~2016-01-26 20:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 21:53 mtd: gpmi: issue with raw access support Han Xu
2016-01-26  6:39 ` Boris Brezillon
2016-01-26  6:42 ` [PATCH] remove deprecated oobinfo retrieval Boris Brezillon
2016-01-26  6:42   ` [PATCH] Adapt raw page accesses to match the new raw_read/write implementation Boris Brezillon
2016-01-26 19:59   ` Brian Norris [this message]
2016-01-26 20:15     ` [PATCH] remove deprecated oobinfo retrieval Han Xu
2016-01-26 20:16     ` 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=20160126195941.GA118766@google.com \
    --to=computersforpeace@gmail.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=shijie.huang@arm.com \
    --cc=xhnjupt@gmail.com \
    /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.