From: Brian Foster <brian.foster@maxim-ic.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Mike Frysinger <vapier@gentoo.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [BUG] mtdinfo -a: Tries to open NULL pointer for NOR with Eraseblock Regions
Date: Fri, 5 Aug 2011 09:24:15 +0200 [thread overview]
Message-ID: <201108050924.15740.brian.foster@maxim-ic.com> (raw)
In-Reply-To: <CAN8TOE847yECw3zeh42tf=6mC73O33Lr7Lzwpi0FrT-rB9ZYmg@mail.gmail.com>
On Thursday 04 August 2011 19:46:10 Brian Norris wrote:
> On Tue, Jul 26, 2011 at 12:21 AM, Brian Foster <brian.foster@maxim-ic.com> wrote:
> > The list was easy to find; what I could not find was
> > any indication of how/where bugs should be reported.
>
> Hmm, it seems like maybe the closest info is hidden away at:
> http://www.linux-mtd.infradead.org/doc/ubifs.html#L_how_send_bugreport
> But much of this refers to UBIFS-specific stuff. Perhaps the
> site should be updated.
Indeed. I don't recall finding that (but as you say,
this is not a UBIFS issue per se). May I suggest an
entry in the FAQ?
>[ ... ]
> Anyway, since I don't have these types of flash [with region_info]
> readily available, I don't even use these options :) And apparently,
> one of the biggest contributors for mtd-utils, Mike Frysinger,
> doesn't use region_info either...
I've no idea why all(? I think!) of our embedded systems
reference designs _do_ use such Flashes. The designer's
on vacation now (this is August, and it is France, hence
just about everybody's on vacation .... !) or I'd ask if
there's any reason.
cheers!
-blf-
--
Brian FOSTER
Principal MTS, Software
Maxim Integrated Products (Microcontroller BU), formerly Innova Card
Web : http://www.maxim-ic.com/
next prev parent reply other threads:[~2011-08-05 7:25 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
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 [this message]
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=201108050924.15740.brian.foster@maxim-ic.com \
--to=brian.foster@maxim-ic.com \
--cc=computersforpeace@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox