| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 11 Oct 2012 07:41:37 -0700 From: Tony Lindgren <tony@...mide.com> To: Ivan Djelic <ivan.djelic@...rot.com> Cc: "Philip, Avinash" <avinashphilip@...com>, afzal@...com, "dwmw2@...radead.org" <dwmw2@...radead.org>, "artem.bityutskiy@...ux.intel.com" <artem.bityutskiy@...ux.intel.com>, "linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-omap@...r.kernel.org" <linux-omap@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org> Subject: Re: [PATCH 4/4] mtd: nand: omap2: Add data correction support * Ivan Djelic <ivan.djelic@...rot.com> [121011 01:23]: > > I don't know which way is better for the OMAP community: > 1. Unifying ECC modes = loosing the constant polynomial benefits, but gaining RBL compat and simplifying code > 2. Keeping separate ECC modes = code bloat > > Tony, do you have an opinion on this ? Well right now I'm mostly interested in making device drivers independent of the arch/arm/*omap*/* code. That's where Afzal's patches help quite a bit, so let's get those in first. So from that point of view, option #1 above sounds better as the first step :) Ideally of course option #1 should not limit us from adding extra features in the long run. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists