From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: MTD Maling List <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] UBI: block: do not use term "attach"
Date: Tue, 4 Mar 2014 11:39:03 -0300 [thread overview]
Message-ID: <20140304143901.GC8826@localhost> (raw)
In-Reply-To: <1393942396.6302.7.camel@sauron.fi.intel.com>
On Tue, Mar 04, 2014 at 04:13:16PM +0200, Artem Bityutskiy wrote:
> On Tue, 2014-03-04 at 10:59 -0300, Ezequiel Garcia wrote:
> > On Tue, Mar 04, 2014 at 02:57:38PM +0200, Artem Bityutskiy wrote:
> > > On Tue, 2014-03-04 at 12:02 +0200, Artem Bityutskiy wrote:
> > > > + * This feature is compiled in the UBI core, and adds a 'block' parameter
> > > > + * to allow early creation of block devices on top of UBI volumes. Runtime
> > > > + * block creation/removal for UBI volumes is provided through two UBI ioctls:
> > > > + * UBI_IOCVOLATTBLK and UBI_IOCVOLDETBLK.
> > > > */
> > >
> > > I think the ioctl names should also be consistent.
> > > s/AT/CR/, s/DET/RM/, may be?
> > >
> >
> > Ah, yes. Good catch.
> >
> > Let's write them down, so we can see how they result: UBI_IOCVOLCRBLK,
> > UBI_IOCVOLRMBLK. Aren't these too unreadable?
>
> Dunno, the other ones are similarly unreadable.
>
Yes, indeed.
> > How about something along UBI_IOCBLK_CREAT UBI_IOCBLK_RM ?
>
> Well, would be a little inconsistent, but more readable, yes.
Indeed, it's less consistent.
> Usually
> ioctl names to not have underscores, though, no?
>
A quick grep shows some ioctls follow that rule, some don't.
I'd say it's your call.
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
prev parent reply other threads:[~2014-03-04 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 10:02 [PATCH] UBI: block: do not use term "attach" Artem Bityutskiy
2014-03-04 10:46 ` Ezequiel Garcia
2014-03-04 12:57 ` Artem Bityutskiy
2014-03-04 13:59 ` Ezequiel Garcia
2014-03-04 14:13 ` Artem Bityutskiy
2014-03-04 14:39 ` Ezequiel Garcia [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=20140304143901.GC8826@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.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