All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Richard Weinberger <richard@nod.at>, linux-mtd@lists.infradead.org
Subject: Re: [PATCH v2] ubi-utils: Add ubiblock tool
Date: Mon, 7 Apr 2014 08:48:37 -0300	[thread overview]
Message-ID: <20140407114837.GC544@arch.cereza> (raw)
In-Reply-To: <1396870403.17040.26.camel@sauron.fi.intel.com>

On Apr 07, Artem Bityutskiy wrote:
> On Sat, 2014-04-05 at 17:33 -0300, Ezequiel Garcia wrote:
> > Hello Artem, Richard:
> > 
> > On Mar 14, Ezequiel Garcia wrote:
> > > With the addition of block device access to UBI volumes, we now
> > > add a simple userspace tool to access the new ioctls.
> > > 
> > > Usage of this tool is as simple as it gets:
> > > 
> > >   $ ubiblock --create /dev/ubi0_0
> > > 
> > > will create a new block device /dev/ubiblock0_0, and
> > > 
> > >   $ ubiblock --remove /dev/ubi0_0
> > > 
> > 
> > After using this for something else than silly tests, I've found this
> > usage is actually a bit braindead :-)
> > 
> > The user will probably want to create a block device based on the volume's
> > name or ID, and not just the node path. In particular, using the name is
> > probably the most useful case, given the atomic ubi volume rename feature.
> > 
> > Therefore, I'd like to see this fixed, but I'm not entirely sure what's the
> > best approach. Here are my ideas so far to identify a volume:
> > 
> >   * Follow the convention of ubirmvol:
> > 
> >     ubiblock --create /dev/ubi0_0 (like we have now)
> >     ubiblock --create <UBI device node file name>
> > 	     [-n <volume id>] [--vol_id=<volume id>]
> >              [-N <volume name>] [--name=<volume name>]
> > 
> >   * Implement something matching the mount command usage. For example,
> > 
> >     ubiblock --create /dev/ubi0_0 (like we have now)
> >     ubiblock --create ubi0:name
> >     ubiblock --create ubi0_0
> > 
> >   * All of them?
> > 
> > To be honest, I don't have any preference.
> 
> Oh, and I released your tool before I read this e-mail.
> 

Oh, no problem. It's my fault for not giving enough thought to this.

> Well, this means that your new changes need to be compatible. Sorry for
> this. Sure, go ahead with the improvements. I also do not have
> preferences. Try to be consistent with other tools, change them too if
> necessary, implement what makes sense and useful.
> 

Right then. I'll cook a patch, hopefully today!
-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

      reply	other threads:[~2014-04-07 11:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-14 14:13 [PATCH] ubi-utils: Add ubiblock tool Ezequiel Garcia
2014-03-14 14:19 ` Ezequiel Garcia
2014-03-14 14:25 ` [PATCH v2] " Ezequiel Garcia
2014-03-21 18:09   ` Ezequiel Garcia
2014-03-25  7:52   ` Artem Bityutskiy
2014-03-25  8:08     ` Artem Bityutskiy
2014-03-25  8:14       ` Artem Bityutskiy
2014-03-29 20:24     ` Ezequiel Garcia
2014-03-31  9:45       ` Artem Bityutskiy
2014-03-31 17:13         ` Brian Norris
2014-04-05 20:33   ` Ezequiel Garcia
2014-04-07 11:33     ` Artem Bityutskiy
2014-04-07 11:48       ` 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=20140407114837.GC544@arch.cereza \
    --to=ezequiel.garcia@free-electrons.com \
    --cc=dedekind1@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.