public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
Cc: "Brian Norris" <computersforpeace@gmail.com>,
	linux-mtd@lists.infradead.org,
	"Guido Martínez" <guido@vanguardiasur.com.ar>
Subject: Re: [RFC] ubi: updatevol: Support volume to volume update
Date: Thu, 17 Jul 2014 08:34:13 +0300	[thread overview]
Message-ID: <1405575253.5423.110.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1405527597-11394-1-git-send-email-ezequiel@vanguardiasur.com.ar>

On Wed, 2014-07-16 at 13:19 -0300, Ezequiel Garcia wrote:
> This commit adds the support for ubiupdatevol to recieve a UBI volume
> as the second parameter. This could be useful to update a UBI volume,
> from another UBI volume present in the system, for instance when
> a redundant scheme is used.

No objections to adding such functionality.

      reply	other threads:[~2014-07-17  5:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-16 16:19 [RFC] ubi: updatevol: Support volume to volume update Ezequiel Garcia
2014-07-17  5:34 ` Artem Bityutskiy [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=1405575253.5423.110.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=computersforpeace@gmail.com \
    --cc=ezequiel@vanguardiasur.com.ar \
    --cc=guido@vanguardiasur.com.ar \
    --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