From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail2.shareable.org ([80.68.89.115]) by bombadil.infradead.org with esmtps (Exim 4.69 #1 (Red Hat Linux)) id 1Ml2cU-0008TK-8I for linux-mtd@lists.infradead.org; Tue, 08 Sep 2009 15:28:39 +0000 Date: Tue, 8 Sep 2009 16:28:13 +0100 From: Jamie Lokier To: Artem Bityutskiy Subject: Re: [RFC] extending nand_ecclayout.eccpos once again Message-ID: <20090908152813.GC5579@shareable.org> References: <20090902093045.GB7377@prithivi.gnumonks.org> <1252390415.5060.38.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1252390415.5060.38.camel@localhost> Cc: Kukjin Kim , Jin-Sung Yang , Ilho Lee , Marc Zyngier , linux-mtd@lists.infradead.org, Harald Welte , David Woodhouse List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Artem Bityutskiy wrote: > Can we instead assume that exposing ECC layout to user-space is jut bad > idea, deprecate current layout ABI, and do not do this anymore. > > I mean, really, ECC layout is generally not user's concern. Just do not > expose it and problem is solved. > > Is it absolutely necessary to have expose this stuff to user-space? Let's rephrase that question. What tools use this information? -- Jamie