linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] ubiformat: correct "non-ubifs" warning message
Date: Mon, 07 Apr 2014 13:45:21 +0300	[thread overview]
Message-ID: <1396867521.17040.14.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1396285384-1757-1-git-send-email-computersforpeace@gmail.com>

On Mon, 2014-03-31 at 10:03 -0700, Brian Norris wrote:
> UBI's raw flash scan actually scans for UBI data, not UBIFS data (there
> *are* UBI users that are not UBIFS!), so correct the warning message.
> This also matches the comment in libscan.h.
> 
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>

Pushed to mtd-utils, thanks!

-- 
Best Regards,
Artem Bityutskiy

      reply	other threads:[~2014-04-07 10:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 17:03 [PATCH] ubiformat: correct "non-ubifs" warning message Brian Norris
2014-04-07 10:45 ` 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=1396867521.17040.14.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=computersforpeace@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).