From: Trent Piepho <tpiepho@freescale.com>
To: Artem Bityutskiy <dedekind@infradead.org>
Cc: "Jörn Engel" <joern@logfs.org>,
linux-mtd-bounces@lists.infradead.org,
"'Bruce Leonard'" <brucle@earthlink.net>,
Bruce_Leonard@selinc.com, linux-kernel@vger.kernel.org,
"Tim Anderson" <tanderson@mvista.com>,
linux-mtd@lists.infradead.org,
"'Andrew Morton'" <akpm@linux-foundation.org>,
"David Woodhouse" <dwmw2@infradead.org>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 2/2][MTD] Add support for > 2GiB MTD devices
Date: Wed, 27 Aug 2008 12:44:35 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0808271243200.3610@t2.domain.actdsltmp> (raw)
In-Reply-To: <1219848463.18027.166.camel@sauron>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: TEXT/PLAIN; charset=X-UNKNOWN, Size: 1012 bytes --]
On Wed, 27 Aug 2008, Artem Bityutskiy wrote:
> > On Wed, 2008-08-27 at 16:34 +0200, Jörn Engel wrote:
> > They certainly can, but should they? There may be some reason to prefer
> > sysfs that should be self-evident - except that I'm a bit thick and seem
> > to need it spelled out. Or maybe I've just become disillusioned with
> > the practice of replacing crappy interfaces (ioctl here) with other
> > crappy interfaces (sysfs here) and having to support both for all
> > eternity. sysctl, ioctl, proc, sysfs, debugfs, netlink, ... -
> > individually they all suck in their own peculiar way. But together they
> > create a mess I no longer dare to name.
>
> The plus of sysfs I see is that I can add more files to expose more
> information in sysfs, while I can not change MEMGETINFO ioctl. E.g., I
> need to expose sub-page size to user-space, and I cannot do this with
> MEMGETINFO.
You can do this with ioctls, if you designed them with extra space and
versioning from the beginning.
prev parent reply other threads:[~2008-08-27 19:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 2:00 Bruce Leonard
2008-08-26 23:55 ` Andrew Morton
2008-08-27 1:21 ` Bruce_Leonard
2008-08-27 1:40 ` Tim Anderson
2008-08-27 2:08 ` Andrew Morton
2008-08-27 2:42 ` Bruce_Leonard
2008-08-27 5:56 ` Artem Bityutskiy
2008-08-27 6:01 ` Tim Anderson
2008-08-27 6:03 ` Artem Bityutskiy
2008-08-27 6:20 ` Tim Anderson
2008-08-27 6:35 ` David Woodhouse
2008-08-27 6:49 ` Ricard Wanderlof
2008-08-27 7:08 ` Artem Bityutskiy
2008-08-27 7:10 ` Bruce Leonard
2008-08-27 6:38 ` Artem Bityutskiy
2008-08-27 8:39 ` Alan Cox
2008-08-27 9:01 ` David Woodhouse
2008-08-27 14:34 ` Jörn Engel
2008-08-27 14:47 ` Artem Bityutskiy
2008-08-27 15:25 ` Jörn Engel
2008-08-29 5:48 ` Artem Bityutskiy
2008-08-29 10:23 ` Jörn Engel
2008-08-29 12:19 ` David Woodhouse
2008-08-27 19:44 ` Trent Piepho [this message]
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=Pine.LNX.4.64.0808271243200.3610@t2.domain.actdsltmp \
--to=tpiepho@freescale.com \
--cc=Bruce_Leonard@selinc.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=brucle@earthlink.net \
--cc=dedekind@infradead.org \
--cc=dwmw2@infradead.org \
--cc=joern@logfs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd-bounces@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=tanderson@mvista.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
all inboxes | Powered by JetHome®