From: Michal Suchanek <hramrach@gmail.com>
To: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Michal Suchanek <hramrach@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mtd@lists.infradead.org
Subject: [PATCH v3 0/5] improve mtdpart robustness
Date: 18 Aug 2015 15:34:06 -0000 [thread overview]
Message-ID: <cover.1439911625.git.hramrach@gmail.com> (raw)
Hello,
this patch series addresses
- compiling in a mtd partitioning scheme may render a mtd device inacessible
- ofpart can fail when subnodes of mtd device node exist
eg. s3c64xx spi controller-data
v3 updates the last patch
- address possible memory leak
- use more generic name for partition node
Thanks
Michal
Michal Suchanek (5):
mtd: mtdpart: add debug prints to partition parser.
mtd: mtdpart: Do not fail mtd probe when parsing partitions fails.
mtd: ofpart: update devicetree binding specification
mtd: ofpart: document the lock flag.
mtd: ofpart: move ofpart partitions to a dedicated dt node
.../devicetree/bindings/mtd/partition.txt | 69 +++++++++++++---------
drivers/mtd/mtdpart.c | 14 ++++-
drivers/mtd/ofpart.c | 63 ++++++++++++++------
3 files changed, 99 insertions(+), 47 deletions(-)
--
2.1.4
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2015-08-18 15:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 15:34 Michal Suchanek [this message]
2015-08-18 15:34 ` [PATCH v3 1/5] mtd: mtdpart: add debug prints to partition parser Michal Suchanek
2015-10-11 20:00 ` Brian Norris
2015-08-18 15:34 ` [PATCH v3 2/5] mtd: mtdpart: Do not fail mtd probe when parsing partitions fails Michal Suchanek
[not found] ` <97366073dfe93b478f24e2fc30ca818326906e0a.1439911625.git.hramrach-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-10-11 20:03 ` Brian Norris
2015-10-27 1:44 ` Brian Norris
2015-08-18 15:34 ` [PATCH v3 3/5] mtd: ofpart: update devicetree binding specification Michal Suchanek
[not found] ` <e47db0c8eeaeb11353bcb2f4dcd138e813c3ecd7.1439911625.git.hramrach-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-10-11 20:04 ` Brian Norris
2015-10-27 2:01 ` Brian Norris
2015-10-27 4:35 ` Rob Herring
[not found] ` <CAL_JsqJ4Ha7R92=6xkwYXZjpEprjWoVxyXM6cG=yykVoTMH-vw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-10-27 22:50 ` Brian Norris
2015-10-28 0:45 ` Rob Herring
2015-08-18 15:34 ` [PATCH v3 4/5] mtd: ofpart: document the lock flag Michal Suchanek
2015-10-11 20:04 ` Brian Norris
2015-10-27 1:47 ` Brian Norris
2015-08-18 15:34 ` [PATCH v3 5/5] mtd: ofpart: move ofpart partitions to a dedicated dt node Michal Suchanek
[not found] ` <78e45e51c94899f92ec5d189846c5dd5cf9d8f7a.1439911625.git.hramrach-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-10-31 0:21 ` 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=cover.1439911625.git.hramrach@gmail.com \
--to=hramrach@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).