linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Artem Bityutskiy <dedekind1@gmail.com>, linux-mtd@lists.infradead.org
Cc: Brian Norris <computersforpeace@gmail.com>
Subject: Re: [PATCH v2] ubi-utils: Add ubiblock tool
Date: Fri, 21 Mar 2014 15:09:56 -0300	[thread overview]
Message-ID: <20140321180955.GB8890@arch> (raw)
In-Reply-To: <1394807124-25916-1-git-send-email-ezequiel.garcia@free-electrons.com>

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
> 
> will remove the device.
> 
> Signed-off-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
> ---

Ping?

I'm wondering how's the release cycle for this. Is it possible
to make a release more or less soon, so this new ubiblock tool
is available?
-- 
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com

  reply	other threads:[~2014-03-21 18:10 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 [this message]
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

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=20140321180955.GB8890@arch \
    --to=ezequiel.garcia@free-electrons.com \
    --cc=computersforpeace@gmail.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;
as well as URLs for NNTP newsgroup(s).