public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org,
	"Eric W. Biederman" <ebiederman@lnxi.com>
Subject: Re: blkmtd and name_to_dev_t
Date: Tue, 4 Apr 2006 10:30:20 +0200	[thread overview]
Message-ID: <20060404083019.GA9747@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <4431E304.6020908@zytor.com>

On Mon, 3 April 2006 20:07:48 -0700, H. Peter Anvin wrote:
> Eric W. Biederman wrote:
> 
> I thought (am I wrong?) that blkmtd referred to using a block device as 
> an MTD device.  Either which way, Jörn tells me that blkmtd is 
> deprecated by block2mtd anyway, and only retained for boot support, 
> which is pretty easy to do in klibc.

You are not wrong.

A possibly better way to deliver the same functionality (jffs2 rootfs
on block device through emulation) might be to add transparent
translation support to jffs2.  Something that will make "mount
/dev/hda1 /mnt -t jffs2" work.  How exactly the code for this should
look, I don't know yet.  But given that jffs2 is the only sane user of
bd->mtd translation, it looks like the Right Thing to me.

> >So I suggest what happens is that we deprecate blkmtd in 
> >Documentation/FeatureRemoval
> >of 2.6.17 and delete it in the -mm tree.
> >
> >Then you can merge klibc.
> >
> >Does any one have a problem with that plan?
> 
> That certainly works for me.  Jörn indicated he's going to sign off on a 
> patch to remove blkmtd, which will solve my problem.

Once the coffee kicks in, yes.  Good morning everyone.

Ordinarily, we should go through the usual 1 year deprecation period
for blkmtd.  But in this case I find it justified to pull the support
immediatly:
o An alternative exists that hasn't had  bug report for > 1 year.
o Most embedded people tend to use ancient kernels with custom patches
  from mtd cvs and elsewhere, so the 1 year warning period neither
  helps nor hurts them too much.
o It's in the way of klibc.  The problems caused by pulling blkmtd
  support are fairly low, while the problems caused by delaying klibc
  can be fairly substantial.  At best, this would be a severe burden
  on hpa's time.

That said, deprecating the driver in -linus and removing it in -mm
until klibc is merged to -linus sounds like a good idea.  Will do
that.

Jörn

-- 
Anything that can go wrong, will.
-- Finagle's Law

  reply	other threads:[~2006-04-04  8:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060329232520.1677d2b3.akpm@osdl.org>
     [not found] ` <442C0494.2040609@zytor.com>
     [not found]   ` <20060330114014.53150d1b.akpm@osdl.org>
2006-03-30 23:36     ` blkmtd and name_to_dev_t H. Peter Anvin
2006-03-31  8:38       ` Jörn Engel
2006-03-31 15:10         ` H. Peter Anvin
2006-04-04  2:56       ` Eric W. Biederman
2006-04-04  3:07         ` H. Peter Anvin
2006-04-04  8:30           ` Jörn Engel [this message]
2006-04-04  8:42             ` Artem B. Bityutskiy
2006-04-04  8:46               ` Jörn Engel
2006-04-04  8:57                 ` Artem B. Bityutskiy
2006-04-04  3:11         ` Josh Boyer

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=20060404083019.GA9747@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=dwmw2@infradead.org \
    --cc=ebiederman@lnxi.com \
    --cc=hpa@zytor.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox