Linux-mtd Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Karl Beldan <karl.beldan@gmail.com>
Cc: David Woodhouse <dwmw2@infradead.org>, linux-mtd@lists.infradead.org
Subject: Re: [RFC] do_mounts: Allow mtd names for non-flash block filesystems
Date: Mon, 11 Oct 2010 22:24:23 +0300	[thread overview]
Message-ID: <1286825063.1742.13.camel@brekeke> (raw)
In-Reply-To: <1286398974-12114-1-git-send-email-karl.beldan@gmail.com>

On Wed, 2010-10-06 at 23:02 +0200, Karl Beldan wrote:
> Hi,
> 
> I have been using this tweak for some time now, and I am getting tired of 
> having to resort to it so often.
> It allows to pass such cmdline root as: 
>  "root=mtdb:ubivolx rootfstype=squashfs"
> I am pretty sure many people use squashfs/cramfs filesystems on top of nand, 
> for example, and I thought that this might initiate discussion.
> 
> -- 
> Karl
> 
> Signed-off-by: Karl Beldan <karl.beldan@gmail.com>
> ---
>  init/do_mounts.c |   15 +++++++++++++--
>  1 files changed, 13 insertions(+), 2 deletions(-)

Dunno... 

First of all, if you have to do this, let it be mtdblock, not mtdb - no
need to breed aliases.

But how about teaching squashfs to understand mtdX and mtd:name syntax
instead?

-- 
Best Regards,
Artem Bityutskiy (Битюцкий Артём)

  parent reply	other threads:[~2010-10-11 19:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-06 21:02 [RFC] do_mounts: Allow mtd names for non-flash block filesystems Karl Beldan
2010-10-06 21:22 ` Karl Beldan
2010-10-11 19:24 ` Artem Bityutskiy [this message]
2010-10-12 13:16   ` Karl Beldan
2010-10-12 14:27     ` Artem Bityutskiy
2010-10-12 15:11       ` Karl Beldan
2010-10-12 15:27         ` Artem Bityutskiy
2010-10-12 15:51           ` Karl Beldan
2010-10-13 10:35     ` Peter Korsgaard
2010-10-13 11:16       ` Karl Beldan

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=1286825063.1742.13.camel@brekeke \
    --to=dedekind1@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=karl.beldan@gmail.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