From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from va3ehsobe003.messaging.microsoft.com ([216.32.180.13] helo=va3outboundpool.messaging.microsoft.com) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1UeyYI-000584-7l for linux-mtd@lists.infradead.org; Wed, 22 May 2013 02:13:19 +0000 Message-ID: <519C2A3C.20709@freescale.com> Date: Wed, 22 May 2013 10:15:24 +0800 From: Huang Shijie MIME-Version: 1.0 To: Vikram Narayanan Subject: Re: [PATCH v6 05/10 fix] mtd: get the ECC info from the Extended Parameter Page References: <51966AA7.7050007@gmail.com> <1369015705-4720-1-git-send-email-b32955@freescale.com> <5199BD45.5090100@gmail.com> <5199C159.6020401@freescale.com> In-Reply-To: Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: quoted-printable Cc: linux-mtd@lists.infradead.org, Brian Norris , dwmw2@infradead.org, lkml , dedekind1@gmail.com List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , =D3=DA 2013=C4=EA05=D4=C222=C8=D5 00:35, Vikram Narayanan =D0=B4=B5=C0: > What if we do like this? Let's do a strict check for now. ("EPPS") > If some chip manufacturer had _strictly_ followed the spec, i.e., any > two bytes are valid. > Then make the code comply with the spec. > Any comments? Agreed. I will send a new patch for this. thanks for the comment. Huang Shijie