From: Thomas Chou <thomas@wytron.com.tw>
To: Mike Frysinger <vapier@gentoo.org>
Cc: linux-mtd@lists.infradead.org, Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: [PATCH] mkfs.jffs2: fix devtable count as mkfs.ubifs does
Date: Fri, 31 Dec 2010 13:54:47 +0800 [thread overview]
Message-ID: <4D1D7027.3070503@wytron.com.tw> (raw)
In-Reply-To: <AANLkTinuOGP7=97UOq5eRe+FxNq3zwKnQQUdCaLT_OqC@mail.gmail.com>
On 12/31/2010 01:08 PM, Mike Frysinger wrote:
> On Thu, Dec 30, 2010 at 22:16, Thomas Chou wrote:
>> The counting was incorrect. Follow that of mkfs.ubifs.
>
> hmm, sounds like we should rip the stuff out of both and put into
> lib/devtable.c. feel up to the challenge ?
> -mike
>
Sound great. But I am lost in the maze of kernel v2.6.37-rc and not
ready to come up with this right now.
- Thomas
next prev parent reply other threads:[~2010-12-31 5:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 7:31 mkfs.jffs2 failed to create repeated dev nodes from device_table.txt Thomas Chou
2010-12-31 1:45 ` [PATCH] mkfs.jffs2: fix repeated dev nodes Thomas Chou
2011-01-16 18:51 ` Artem Bityutskiy
2010-12-31 3:16 ` [PATCH] mkfs.jffs2: fix devtable count as mkfs.ubifs does Thomas Chou
2010-12-31 5:08 ` Mike Frysinger
2010-12-31 5:54 ` Thomas Chou [this message]
2011-01-16 18:51 ` 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=4D1D7027.3070503@wytron.com.tw \
--to=thomas@wytron.com.tw \
--cc=dedekind1@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;
as well as URLs for NNTP newsgroup(s).