public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: "Bean Huo 霍斌斌 (beanhuo)" <beanhuo@micron.com>,
	"dedekind1@gmail.com" <dedekind1@gmail.com>,
	"adrian.hunter@intel.com" <adrian.hunter@intel.com>,
	"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
	"baruch@tkos.co.il" <baruch@tkos.co.il>,
	"asierra@xes-inc.com" <asierra@xes-inc.com>,
	"guz.fnst@cn.fujitsu.com" <guz.fnst@cn.fujitsu.com>,
	"gsi@denx.de" <gsi@denx.de>,
	"Boris Brezillon" <boris.brezillon@free-electrons.com>
Cc: "David Woodhouse" <dwmw2@infradead.org>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"Frank Liu 刘群 (frankliu)" <frankliu@micron.com>,
	"Andrea Scian" <rnd4@dave-tech.it>,
	"Karl Zhang 张双锣 (karlzhang)" <karlzhang@micron.com>,
	"Iwo Mergler" <Iwo.Mergler@netcommwireless.com>,
	"Jeff Lauruhn (jlauruhn)" <jlauruhn@micron.com>,
	"Stefan Roese" <sr@denx.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/9] drivers:mtd:UBI: add bakvol module for MLC NAND paired page issue
Date: Wed, 30 Sep 2015 08:55:20 +0200	[thread overview]
Message-ID: <560B8758.7010002@nod.at> (raw)
In-Reply-To: <A765B125120D1346A63912DDE6D8B6310BF4D4C6@NTXXIAMBX02.xacn.micron.com>

Bean,

Am 30.09.2015 um 07:31 schrieb Bean Huo 霍斌斌 (beanhuo):
>> As stated before, using OOB in UBI is not going to happen unless proven that
>> there is absolutely no other way to solve the paired pages problem.
>>
>> Nacked-by: Richard Weinberger <richard@nod.at>
>>
>> Sorry,
>> //Richard
> 
> Hi, Richard
> Thanks for your concern. I am a new patch submitter.
> Can you tell me Nacked-by means?

I basically means that I'm (as maintainer) really unhappy with this patches
and don't see a way to get them merged as the whole concept is not acceptable.

> By the way, Do you review my patches series ? I don't backup duplicated data in OOB .
> Can you specify which sector codes ? so that I can explain it in detail.

Okay. Maybe both Boris and I misread your code, can you please explain in detail
what functions like check_original_data() or mtd_write_dual_plane_oob() do?

Thanks,
//richard

  reply	other threads:[~2015-09-30  6:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28  7:02 [PATCH 0/9] drivers:mtd:UBI: add bakvol module for MLC NAND paired page issue Bean Huo 霍斌斌 (beanhuo)
2015-09-28  7:41 ` Boris Brezillon
2015-09-28  8:16   ` Bean Huo 霍斌斌 (beanhuo)
2015-09-29  9:28 ` Richard Weinberger
2015-09-30  5:31   ` Bean Huo 霍斌斌 (beanhuo)
2015-09-30  6:55     ` Richard Weinberger [this message]
2015-10-02 10:28       ` Richard Weinberger
2015-10-08  2:10         ` Bean Huo 霍斌斌 (beanhuo)
2015-10-08  0:27       ` Bean Huo 霍斌斌 (beanhuo)
2015-09-30  7:33     ` Boris Brezillon
2015-10-08  0:49       ` Bean Huo 霍斌斌 (beanhuo)

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=560B8758.7010002@nod.at \
    --to=richard@nod.at \
    --cc=Iwo.Mergler@netcommwireless.com \
    --cc=adrian.hunter@intel.com \
    --cc=asierra@xes-inc.com \
    --cc=baruch@tkos.co.il \
    --cc=beanhuo@micron.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=frankliu@micron.com \
    --cc=gsi@denx.de \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=jlauruhn@micron.com \
    --cc=karlzhang@micron.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=rnd4@dave-tech.it \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox