From: Adrian Hunter <adrian.hunter@nokia.com>
To: Corentin Chary <corentincj@iksaif.net>
Cc: "util-linux-ng@vger.kernel.org" <util-linux-ng@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"dedekind1@gmail.com" <dedekind1@gmail.com>
Subject: Re: [PATCH] UBIFS: Add /dev/ubiX_Y naming scheme in open_ubi
Date: Fri, 25 Sep 2009 14:37:50 +0300 [thread overview]
Message-ID: <4ABCAB8E.5070604@nokia.com> (raw)
In-Reply-To: <1253832477-29064-1-git-send-email-corentincj@iksaif.net>
Corentin Chary wrote:
> This is needed to use $ mount /dev/ubi0_0 /mnt/nand
> You'll also need a recent libblkid with UBI and UBIFS
> support.
>
> Signed-off-by: Corentin Chary <corentincj@iksaif.net>
> ---
> fs/ubifs/super.c | 12 ++++++++----
> 1 files changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/fs/ubifs/super.c b/fs/ubifs/super.c
> index 7e2b3d4..38320ad 100644
> --- a/fs/ubifs/super.c
> +++ b/fs/ubifs/super.c
> @@ -1843,10 +1843,11 @@ const struct super_operations ubifs_super_operations = {
> * @mode: UBI volume open mode
> *
> * There are several ways to specify UBI volumes when mounting UBIFS:
> - * o ubiX_Y - UBI device number X, volume Y;
> - * o ubiY - UBI device number 0, volume Y;
> - * o ubiX:NAME - mount UBI device X, volume with name NAME;
> - * o ubi:NAME - mount UBI device 0, volume with name NAME.
> + * o /dev/ubiX_Y - UBI device number X, volume Y;
> + * o ubiX_Y - UBI device number X, volume Y;
> + * o ubiY - UBI device number 0, volume Y;
> + * o ubiX:NAME - mount UBI device X, volume with name NAME;
> + * o ubi:NAME - mount UBI device 0, volume with name NAME.
> *
> * Alternative '!' separator may be used instead of ':' (because some shells
> * like busybox may interpret ':' as an NFS host name separator). This function
> @@ -1858,6 +1859,9 @@ static struct ubi_volume_desc *open_ubi(const char *name, int mode)
> int dev, vol;
> char *endptr;
>
> + if (!strncmp("/dev/", name, 5))
> + name = name + 5;
> +
> if (name[0] != 'u' || name[1] != 'b' || name[2] != 'i')
> return ERR_PTR(-EINVAL);
Is this for the kernel?
I do not think UBIFS should interpret the file name. It should
work off the major and minor numbers from the device node
irrespective of what its path name or file name is.
next prev parent reply other threads:[~2009-09-25 11:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-24 11:11 [PATCH 0/3] Add support for UBI and UBIFS Corentin Chary
2009-08-24 11:11 ` [PATCH 1/3] blkid: add UBI volume support Corentin Chary
2009-08-24 11:11 ` [PATCH 2/3] blkid: add ubifs support Corentin Chary
2009-08-24 11:11 ` [PATCH 3/3] blkid: add UBIFS test image to blkid test suite Corentin Chary
2009-09-02 9:24 ` [PATCH 1/3] blkid: add UBI volume support Karel Zak
2009-09-02 10:10 ` Artem Bityutskiy
2009-09-18 10:52 ` Corentin Chary
2009-09-19 1:23 ` Theodore Tso
2009-09-24 14:14 ` Karel Zak
2009-09-24 21:57 ` Corentin Chary
2009-09-25 7:19 ` Artem Bityutskiy
2009-09-25 7:56 ` Karel Zak
2009-08-31 19:03 ` [PATCH 0/3] Add support for UBI and UBIFS Corentin Chary
2009-08-31 21:25 ` Karel Zak
2009-09-24 14:06 ` Karel Zak
2009-09-24 22:41 ` Corentin Chary
2009-09-24 22:47 ` [PATCH] UBIFS: Add /dev/ubiX_Y naming scheme in open_ubi Corentin Chary
2009-09-25 11:37 ` Adrian Hunter [this message]
2009-09-25 12:27 ` Corentin Chary
2009-09-28 11:39 ` Artem Bityutskiy
2009-09-28 11:53 ` Corentin Chary
2009-09-28 12:02 ` Artem Bityutskiy
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=4ABCAB8E.5070604@nokia.com \
--to=adrian.hunter@nokia.com \
--cc=corentincj@iksaif.net \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=util-linux-ng@vger.kernel.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.