public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Brian Foster <brian.foster@maxim-ic.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH 2/2] ubinfo: fix `--all' for non-consecutive device numbers
Date: Thu, 26 Jan 2012 09:53:04 +0100	[thread overview]
Message-ID: <201201260953.04349.brian.foster@maxim-ic.com> (raw)
In-Reply-To: <1327563110-23966-2-git-send-email-computersforpeace@gmail.com>

On Thursday 26 January 2012 08:31:50 Brian Norris wrote:
> When we have assigned non-consecutive device numbers to our UBI devices [...]
> This patch adds a check to first see if device is present, then continue
> to the next ID if it doesn't exist.
>[ ... ] 

 Looks Ok to me (when used with part 1).

 However, looking at the mtd-utils v1.4.6 ‘mtdinfo.c’,
 is there a similar issue there?  But I have no idea
 how you could get non-consecutive MTD device numbers?

cheers!
	-blf-

-- 
Brian Foster
Principal MTS, Software        |  La Ciotat, France
Maxim Integrated Products      |  Web:  http://www.maxim-ic.com/

  reply	other threads:[~2012-01-26  9:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-26  7:31 [PATCH 1/2] libubi: make `ubi_dev_present()' a library function Brian Norris
2012-01-26  7:31 ` [PATCH 2/2] ubinfo: fix `--all' for non-consecutive device numbers Brian Norris
2012-01-26  8:53   ` Brian Foster [this message]
2012-01-27 18:28     ` Brian Norris
2012-01-30  8:32       ` Brian Foster
2012-01-27 14:51 ` [PATCH 1/2] libubi: make `ubi_dev_present()' a library function Artem Bityutskiy

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=201201260953.04349.brian.foster@maxim-ic.com \
    --to=brian.foster@maxim-ic.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