From: Artem Bityutskiy <dedekind@infradead.org>
To: Nancy <nancydreaming@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] [MTD] [UBI] add block device layer on top of UBI
Date: Tue, 13 May 2008 12:53:11 +0300 [thread overview]
Message-ID: <1210672391.5708.15.camel@sauron> (raw)
In-Reply-To: <bae050c10805122116g4295f202j40e1a8528be5220@mail.gmail.com>
On Tue, 2008-05-13 at 12:16 +0800, Nancy wrote:
> Hi all,
> I think it is my final edition of ubi block device layer code
> based on UBI commit e442c48f84982d0fa10c6b292018241dafca4d65
> Finally, it can support any filesystem based on block device layer.
> eg: FAT, ext2....
> #modprobe ubiblk
> #mkfs.vfat /dev/ubiblock1
> #mount -t vfat /dev/ubiblock1 /mnt/fat
>
> I notice there many people need this function especially our
> Chinese. Hope this helpful :-)
> Here's my implementation:
What is the reason you added this "generic" ubi mtd block stuff? What
for? Also, UBI should not have any explicit block device support - it
should be isolated. It is to ok to add some general support for devices
on top of UBI, like notification about volume size change and so on,
but not explicit block layer support. Gluebi should also get a separate
module, ideally.
Also, the patch suffers from too direct copy-pastes which is not
acceptable.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2008-05-13 9:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 11:17 [PATCH] [MTD] [UBI] add block device layer on top of UBI Nancy
2008-03-04 9:40 ` Nancy
2008-03-04 9:40 ` Artem Bityutskiy
2008-03-04 9:54 ` Nancy
2008-03-04 9:53 ` Artem Bityutskiy
2008-03-04 10:07 ` Nancy
2008-03-04 13:55 ` Nancy
2008-05-13 4:16 ` Nancy
2008-05-13 9:53 ` Artem Bityutskiy [this message]
2008-05-13 13:31 ` Nancy
2008-05-14 13:50 ` Artem Bityutskiy
2008-05-15 4:59 ` Nancy
2008-05-14 18:15 ` N Cheung
2008-05-15 5:54 ` Nancy
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=1210672391.5708.15.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=nancydreaming@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