public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: joern@wohnheim.fh-wedel.de, dwmw2@infradead.org,
	linux-mtd@lists.infradead.org
Subject: blkmtd and name_to_dev_t
Date: Thu, 30 Mar 2006 15:36:24 -0800	[thread overview]
Message-ID: <442C6B78.3060706@zytor.com> (raw)
In-Reply-To: <20060330114014.53150d1b.akpm@osdl.org>

Hello all,

I'm trying to revamp the Linux kernel by moving a lot of (mainly) 
initialization code to "early userspace" -- a tiny userspace carried 
with the kernel image.  This is sometimes referred to as the "klibc" 
project.

I sent a git tree to Andrew Morton for possible integration in -mm, and 
it got rejected due to the fact that the blkmtd driver uses 
name_to_dev_t() when compiled into the kernel, which is removed in the 
klibc tree -- it is now strictly a matter of userspace policy.

I talked to Jörg Engel about this; he indicated that the blkmtd driver 
(which is the one that has this problem) is already deprecated in favour 
of block2mtd.  Hence I'm hesitant to spend a lot of time on this, 
especially in the light of the fact that keeping a 90,000-line patch up 
to date with an evolving kernel is a challenge in itself.

There seems to be a few options, in order from least work to more work:

- Removing the blkmtd driver and tell people to use block2mtd;
- Have kinit intercept blkmtd configuration options and emulate them 
using block2mtd;
- Adjust blkmtd to have a configuration interface, and then make kinit 
configure it.

I would appreciate any opinions on this.  Clearly, I'm eager at getting 
unblocked on this, but my submitting a tree to Andrew which disables a 
driver without the maintainers' OK isn't exactly going to fly :)

For what it's worth, the klibc tree is at:

git://git.kernel.org/pub/scm/linux/kernel/git/hpa/linux-2.6-klibc.git

	-=hpa

       reply	other threads:[~2006-03-30 23:41 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     ` H. Peter Anvin [this message]
2006-03-31  8:38       ` blkmtd and name_to_dev_t 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
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=442C6B78.3060706@zytor.com \
    --to=hpa@zytor.com \
    --cc=dwmw2@infradead.org \
    --cc=joern@wohnheim.fh-wedel.de \
    --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