From: hujianyang <hujianyang@huawei.com>
To: Artem Bityutskiy <dedekind1@gmail.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
Bill Pringlemeir <bpringlemeir@nbsps.com>
Subject: [PATCH RFC v3] ubi-utils: Introduce a utility ubidump
Date: Sat, 20 Sep 2014 12:59:53 +0800 [thread overview]
Message-ID: <541D09C9.4080004@huawei.com> (raw)
Hi all,
It's about two months after the pushing of my v2 patches. I'd like
to resend these v3 patches and discuss with you about the debugging
of UBIFS. I wish you are not tried with this stuff.
I have to say these v3 patches don't make a great difference with
the previous versions. Just simplify, I've removed ubi-level dump.
So the lpt-leb dump is not supported as before. I want to know if
we could start at this version and add other functionality step by
step.
Thanks~!
v1:
http://lists.infradead.org/pipermail/linux-mtd/2014-July/054541.html
v2:
http://lists.infradead.org/pipermail/linux-mtd/2014-July/054831.html
Changes in v3:
- Remove ubi-level dump so we don't need to worry about how to
get ubi-level info from an UBI device.
- Read ubifs stuff by read() ops which is provided by UBI driver.
next reply other threads:[~2014-09-20 5:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-20 4:59 hujianyang [this message]
2014-09-20 5:03 ` [PATCH 1/4] ubi-utils: ubidump compile enable hujianyang
2014-09-26 10:24 ` Artem Bityutskiy
2014-09-20 5:05 ` [PATCH 2/4] ubi-utils: ubidump add libdump hujianyang
2014-09-26 10:28 ` Artem Bityutskiy
2014-09-20 5:06 ` [PATCH 3/4] ubi-utils: ubidump add ubifs-media hujianyang
2014-09-26 10:29 ` Artem Bityutskiy
2014-09-20 5:08 ` [PATCH 4/4] ubi-utils: introduce ubidump hujianyang
2014-09-26 10:31 ` Artem Bityutskiy
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=541D09C9.4080004@huawei.com \
--to=hujianyang@huawei.com \
--cc=bpringlemeir@nbsps.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@gmail.com \
/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).