From: Brian Norris <computersforpeace@gmail.com>
To: Chris Packham <Chris.Packham@alliedtelesis.co.nz>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"andrew@lunn.ch" <andrew@lunn.ch>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"boris.brezillon@free-electrons.com"
<boris.brezillon@free-electrons.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Marek Vasut <marek.vasut@gmail.com>,
Richard Weinberger <richard@nod.at>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
David Oberhollenzer <david.oberhollenzer@sigma-star.at>
Subject: Re: [PATCH v5 3/5] mtd: handle partitioning on devices with 0 erasesize
Date: Fri, 7 Jul 2017 18:14:19 -0700 [thread overview]
Message-ID: <20170708011419.GE55942@google.com> (raw)
In-Reply-To: <ec40da4af0be445b9a1f2ed29e61a547@svr-chch-ex1.atlnz.lc>
On Tue, Jul 04, 2017 at 03:22:52AM +0000, Chris Packham wrote:
> I had someone mention to me in passing that mtdinfo was failing for them
> (crashing with some floating point error). I'm wondering if we've
> created a divide-by-zero problem by reporting 0 erase size in /proc/mtd.
> I don't have any other info and right now I don't have access to the
> system I had with the mchp23lcv1024 sram.
Wouldn't be that surprising. mtdinfo is actually developed under the
"ubi-utils" directory of mtd-utils, and UBI wouldn't know what to do
with and SRAM like that.
Brian
next prev parent reply other threads:[~2017-07-08 1:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 3:21 [PATCH v5 0/5] mtd: mchp23k256: device tree and mchp23lcv1024 Chris Packham
2017-06-02 3:21 ` [PATCH v5 1/5] mtd: mchp23k256: Add OF device ID table Chris Packham
2017-06-02 3:21 ` Chris Packham
2017-06-02 3:21 ` [PATCH v5 2/5] mtd: mchp23k256: switch to mtd_device_register() Chris Packham
2017-06-02 3:21 ` [PATCH v5 3/5] mtd: handle partitioning on devices with 0 erasesize Chris Packham
2017-06-08 23:26 ` Brian Norris
2017-07-04 3:22 ` Chris Packham
2017-07-08 1:14 ` Brian Norris [this message]
2017-06-02 3:21 ` [PATCH v5 4/5] mtd: mchp23k256: add partitioning support Chris Packham
2017-06-08 23:33 ` Brian Norris
2017-06-08 23:40 ` Chris Packham
2017-06-02 3:21 ` [PATCH v5 5/5] mtd: mchp23k256: Add support for mchp23lcv1024 Chris Packham
2017-06-02 5:36 ` [PATCH v5 0/5] mtd: mchp23k256: device tree and mchp23lcv1024 Boris Brezillon
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=20170708011419.GE55942@google.com \
--to=computersforpeace@gmail.com \
--cc=Chris.Packham@alliedtelesis.co.nz \
--cc=andrew@lunn.ch \
--cc=boris.brezillon@free-electrons.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=david.oberhollenzer@sigma-star.at \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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.