From: Artem Bityutskiy <dedekind1@gmail.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Brian Foster <brian.foster@maxim-ic.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
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 17:17:00 +0300 [thread overview]
Message-ID: <1313504225.21711.3.camel@sauron> (raw)
In-Reply-To: <CAN8TOE9NyKqOkfYC6h_44Wf+xs7ZtTjGS+YkLAhLV60FnKB2hQ@mail.gmail.com>
On Mon, 2011-08-15 at 16:13 -0700, Brian Norris wrote:
> This way, we do not rely on guessing any paths; we simply use the
> sysfs information that is exposed, among other purposes, for cases
> cases like this, right? And then (as I stated on another message in
> this thread) we could even support the "region info" on newer kernels,
> if somebody ever does the work to export them. I think this solution
> involves no extra work right now, does not remove valuable features,
> does not make dirty assumptions about node names, and can take
> advantage of new sysfs features in the future. The main downside I see
> is the potential (documented) difference in information printed by
> `mtdinfo --all' vs. `mtdinfo /dev/mtdX'.
Yes, fair enough, just pushed your fix and cleanups, thanks!
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2011-08-16 14:15 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 [this message]
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
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=1313504225.21711.3.camel@sauron \
--to=dedekind1@gmail.com \
--cc=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