From: Lars-Peter Clausen <lars@metafoo.de>
To: dedekind1@gmail.com
Cc: Ben Dooks <ben-linux@fluff.org>,
Kukjin Kim <kgene.kim@samsung.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Holger Freyther <zecke@openmoko.org>
Subject: Re: [PATCH 1/2] MTD: s3c2410_nand: Add option to disable hw ECC at runtime
Date: Thu, 14 Apr 2011 16:48:45 +0200 [thread overview]
Message-ID: <4DA7094D.9070002@metafoo.de> (raw)
In-Reply-To: <1302782911.2796.21.camel@localhost>
On 04/14/2011 02:08 PM, Artem Bityutskiy wrote:
> On Tue, 2011-04-12 at 21:47 +0200, Lars-Peter Clausen wrote:
>> From: Holger Freyther <zecke@openmoko.org>
>>
>> This patch adds a flag to the s3c2410_nand platform data, which configures
>> whether hardware ECC is used.
>>
>> Currently it is only possible to decide whether hw ECC should be used or not at
>> compile time through a config option. But if you want to build a kernel which
>> runs on multiple devices you might have a configuration where some devices
>> require hw ECC and some devices which want software ECC.
>>
>> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
>
> Extending platform data is kind of vetoed in arm tree, I do not think
> the MTD tree can take these changes.
>
That is not my understanding of the situation. But what do you suggest as an
alternative for fixing this issue?
- Lars
next prev parent reply other threads:[~2011-04-14 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 19:47 [PATCH 1/2] MTD: s3c2410_nand: Add option to disable hw ECC at runtime Lars-Peter Clausen
2011-04-12 19:47 ` [PATCH 2/2] ARM: s3c2440: GTA02: Disable hardware ECC by default Lars-Peter Clausen
2011-04-14 12:08 ` [PATCH 1/2] MTD: s3c2410_nand: Add option to disable hw ECC at runtime Artem Bityutskiy
2011-04-14 14:48 ` Lars-Peter Clausen [this message]
2011-04-15 14:01 ` Artem Bityutskiy
2011-04-28 13:51 ` Russell King - ARM Linux
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=4DA7094D.9070002@metafoo.de \
--to=lars@metafoo.de \
--cc=ben-linux@fluff.org \
--cc=dedekind1@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=zecke@openmoko.org \
/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;
as well as URLs for NNTP newsgroup(s).