From: Artem Bityutskiy <dedekind1@gmail.com>
To: dedekind1@gmail.com
Cc: linux-mtd@lists.infradead.org, Daniel Neukomm <Neukomm@vtxmail.ch>
Subject: Re: patch for mkfs.ubifs devtable.c increment in dev_table is wrongly interpreted
Date: Tue, 11 Aug 2009 14:21:04 +0300 [thread overview]
Message-ID: <4A815420.1060802@gmail.com> (raw)
In-Reply-To: <1249973154.19638.30.camel@localhost>
On 08/11/2009 09:45 AM, Artem Bityutskiy wrote:
> On Sun, 2009-08-02 at 16:04 +0200, Daniel Neukomm wrote:
>> patch for mkfs.ubifs devtable.c increment in dev_table is wrongly
>> interpreted
>>
>> with the device table one can add /dev entries to the root file system
>> image.
>> The device table file contains among others the fields minor, start,
>> increment and count.
>> If there is an entry with minor=0 start=0 increment =32 and count=4 the
>> mkfs.ubifs makes
>> 128 device entries, with minor numbers from 0 to 127
>> The correct version makes 4 entries with minor number 0,32,64,96.
>>
>> /dev/mtd c 640 0 0 90 0 0 2 7
>> This gives 14 devices /dev/mtdXX instead of 7 devices.
>> Due to this error mtd_debug info /dev/mtd3 delivers the information of
>> /dev/mtd1 instead of.
>
> Ok, below is how you was supposed to send the patch (without my
> Signed-off-by, of course). I just applied your patch manually (usually
> we use git am for this) and tweaked it.
>
> Please, check that I did not do any mistake. After you have confirmed
> this, I'll push this to the mtd-utils repository.
I've pushed it actually to mtd-utils.git. But please, check it anyway.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2009-08-11 11:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 14:04 patch for mkfs.ubifs devtable.c increment in dev_table is wrongly interpreted Daniel Neukomm
2009-08-03 3:48 ` Mike Frysinger
2009-08-10 7:36 ` Artem Bityutskiy
2009-08-11 6:45 ` Artem Bityutskiy
2009-08-11 11:21 ` Artem Bityutskiy [this message]
2009-08-12 18:27 ` Daniel Neukomm
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=4A815420.1060802@gmail.com \
--to=dedekind1@gmail.com \
--cc=Neukomm@vtxmail.ch \
--cc=linux-mtd@lists.infradead.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 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.