From: David Woodhouse <dwmw2@infradead.org>
To: apgmoorthy <moorthy.apg@samsung.com>
Cc: "'Kyungmin Park'" <kmpark@infradead.org>,
linux-mtd@lists.infradead.org,
"'lkml'" <linux-kernel@vger.kernel.org>,
dedekind@infradead.org
Subject: RE: [ANNOUNCE] [PATCH] [MTD] Flex-OneNAND MTD Driver available.
Date: Fri, 10 Oct 2008 07:34:53 +0100 [thread overview]
Message-ID: <1223620493.28324.90.camel@macbook.infradead.org> (raw)
In-Reply-To: <000b01c92215$ae62d4e0$3dd66c6b@sisodomain.com>
On Mon, 2008-09-29 at 14:58 +0530, apgmoorthy wrote:
> Please do comment on this patch.
>
> "Not to expose whole OOB" suggestion by Kyungmin should be fine ,
> but looking for your suggestion.
I'm working on a revamp of the MTD core which would start exposing
attributes by sysfs, which would mean a lot of the ioctl problems go
away. I suspect it would be OK simply not to export the whole OOB, until
that's done.
I posted other code which can export things in sysfs already -- perhaps
we don't need to wait until the core rewrite is done?
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2008-10-10 6:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19198934.52871221827459790.JavaMail.weblogic@epml16>
2008-09-22 7:11 ` [ANNOUNCE] [PATCH] [MTD] Flex-OneNAND MTD Driver available Kyungmin Park
2008-09-24 12:35 ` apgmoorthy
2008-09-26 0:31 ` Kyungmin Park
2008-09-26 4:51 ` Artem Bityutskiy
2008-09-26 5:30 ` Kyungmin Park
2008-09-26 6:26 ` Artem Bityutskiy
2008-09-26 8:01 ` Amit Kumar Sharma
2008-09-26 8:19 ` Artem Bityutskiy
2008-09-29 9:28 ` apgmoorthy
2008-10-09 22:57 ` Kyungmin Park
2008-10-10 6:34 ` David Woodhouse [this message]
2008-10-16 4:16 apgmoorthy
2008-10-16 4:28 ` Kyungmin Park
2008-10-20 3:01 ` Kyungmin Park
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=1223620493.28324.90.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=dedekind@infradead.org \
--cc=kmpark@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=moorthy.apg@samsung.com \
/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