From: hujianyang <hujianyang@huawei.com>
To: <dedekind1@gmail.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
Bill Pringlemeir <bpringlemeir@nbsps.com>
Subject: Re: [PATCH v5 3/4] ubi-utils: ubidump: introduce ubidump
Date: Mon, 1 Dec 2014 09:45:17 +0800 [thread overview]
Message-ID: <547BC82D.6050608@huawei.com> (raw)
In-Reply-To: <1417098723.5858.90.camel@sauron.fi.intel.com>
On 2014/11/27 22:32, Artem Bityutskiy wrote:
> On Thu, 2014-11-20 at 17:24 +0800, hujianyang wrote:
>> /tmp# ./ubidump /dev/ubi0_0 --lnum 0
>> scan LEB 0:0
>> look at LEB 0:0 (126976 bytes left)
>> scanning superblock node at LEB 0:0
>> look at LEB 0:4096 (122880 bytes left)
>> hit empty space at LEB 0:4096
>> stop scanning LEB 0 at offset 126976
>
> Just do not introduce any options at all. Print all you can right away.
>
> Let's say: no options means auto-detect everything and print everything.
> Since all you can do right now is to dump UBIFS stuff, just do it.
>
> If someone needs more - they will have to start adding options.
>
Got it~!
next prev parent reply other threads:[~2014-12-01 1:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 10:37 [PATCH v5 1/4] ubi-utils: ubidump: add ubifs-media hujianyang
2014-10-22 10:40 ` [PATCH v5 2/4] ubi-utils: ubidump: add libdump hujianyang
2014-10-22 10:43 ` [PATCH v5 3/4] ubi-utils: ubidump: introduce ubidump hujianyang
2014-10-30 8:19 ` Artem Bityutskiy
2014-10-30 8:30 ` Artem Bityutskiy
2014-10-31 2:17 ` hujianyang
2014-10-31 7:32 ` Artem Bityutskiy
2014-10-31 10:55 ` hujianyang
2014-10-31 13:20 ` Artem Bityutskiy
2014-11-20 9:24 ` hujianyang
2014-11-27 14:32 ` Artem Bityutskiy
2014-12-01 1:45 ` hujianyang [this message]
2014-10-22 10:47 ` [PATCH v5 4/4] ubi-utils: ubidump: compile enable hujianyang
2014-10-30 7:51 ` [PATCH v5 1/4] ubi-utils: ubidump: add ubifs-media Artem Bityutskiy
2014-10-30 8:01 ` Artem Bityutskiy
2014-10-31 2:03 ` hujianyang
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=547BC82D.6050608@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 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.