All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Foster <brian.foster@maxim-ic.com>
To: "dedekind1@gmail.com" <dedekind1@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	Mike Frysinger <vapier@gentoo.org>
Subject: Re: [BUG] mtdinfo -a: Tries to open NULL pointer for NOR with Eraseblock Regions
Date: Tue, 16 Aug 2011 09:31:02 +0200	[thread overview]
Message-ID: <201108160931.02543.brian.foster@maxim-ic.com> (raw)
In-Reply-To: <1313381489.2200.19.camel@koala>

On Monday 15 August 2011 06:11:27 Artem Bityutskiy wrote:
> On Tue, 2011-08-09 at 13:34 -0400, Mike Frysinger wrote:
> > On Mon, Aug 8, 2011 at 19:19, Brian Norris wrote:
> > > "Alternatively, --all only prints what it can get,
> > > and --help warns there _may_ be additional data not
> > > printed by --all (and to use ‘mtdinfo /dev/mtd<N>’)."
> > 
> > that's really the only other option of the three.
> > 1: add region_info to sysfs
> > 2: add a warning --all that it could be incomplete
> > 3: have --all use the legacy lookup func to get /dev/mtd#
> 
> How about: make a quick fix and release mtd-utils-1.4.6, then just kill
> the -a option.  [...]

 You should decide what ‘-a’ means:  “all information”
 or “all devices”.  If “all information”, then either a
 bunch of work needs to be done, or else ‘-a’ removed.

 But if “all devices”  — which happens to be both what
 I think it means and how I use it —  then it is very
 useful, at least in my situation where I'm bringing up
 a new SoC and board.  It's a nice summary of what I'm
 usually interested in; if it didn't exist, I'd “have”
 to script it.  And in either case, if and when I do
 need all the information about _a_ device, then I do
 ‘mtdinfo /dev/mtd<N>’.

cheers!
	-blf-
-- 
Brian FOSTER
Principal MTS, Software

Maxim Integrated Products (Microcontroller BU), formerly Innova Card
ZI Athélia IV - Le Forum, Bât. A
Quartier Roumagoua
13600 La Ciotat - France
Phone  : +33 (0)4 42 98 15 35
Fax    : +33 (0)4 42 08 33 19
Email  : brian.foster@maxim-ic.com
Web    : http://www.maxim-ic.com/

  parent reply	other threads:[~2011-08-16  7:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25  9:48 [BUG] mtdinfo -a: Tries to open NULL pointer for NOR with Eraseblock Regions Brian Foster
2011-07-25 17:10 ` Brian Norris
2011-07-26  7:21   ` Brian Foster
2011-08-04 17:46     ` Brian Norris
2011-08-04 22:41       ` Mike Frysinger
2011-08-06  0:09         ` Brian Norris
2011-08-06  1:18           ` Mike Frysinger
2011-08-08  8:16             ` Brian Foster
2011-08-08 23:19             ` Brian Norris
2011-08-09  7:27               ` Brian Foster
2011-08-09 17:34               ` Mike Frysinger
2011-08-09 19:59                 ` Brian Norris
2011-08-15  4:11                 ` Artem Bityutskiy
2011-08-15 23:13                   ` Brian Norris
2011-08-16 14:17                     ` Artem Bityutskiy
2011-08-16  7:31                   ` Brian Foster [this message]
2011-08-16 17:47                     ` Brian Norris
2011-08-08  8:10           ` Brian Foster
2011-08-08  8:40             ` Brian Foster
2011-08-05  7:24       ` Brian Foster
2011-08-06  0:06         ` Brian Norris

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=201108160931.02543.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 \
    --cc=vapier@gentoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.