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] mkfs.ubifs: correct and improve LEB size error prints
Date: Mon, 31 Mar 2014 12:50:02 +0300	[thread overview]
Message-ID: <1396259402.9016.60.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <1395470744-7281-1-git-send-email-computersforpeace@gmail.com>

On Fri, 2014-03-21 at 23:45 -0700, Brian Norris wrote:
> The error message is incorrect for "too small LEB size" -- we were
> printing the minimum I/O size instead of the LEB size.
> 
> At the same time, let's print the max LEB size along with the message
> for "too large LEB size", to be consistent and more helpful.
> 
> Signed-off-by: Brian Norris <computersforpeace@gmail.com>
> 			       UBIFS_MIN_LEB_CNT);

Pushed, thanks!

-- 
Best Regards,
Artem Bityutskiy

      reply	other threads:[~2014-03-31  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-22  6:45 [PATCH] mkfs.ubifs: correct and improve LEB size error prints Brian Norris
2014-03-31  9:50 ` 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=1396259402.9016.60.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).