From: Richard Weinberger <richard@nod.at>
To: Sheng Yong <shengyong1@huawei.com>,
Michael Niarchos <michael.niarchos@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Cannot mount ubifs partition
Date: Thu, 14 May 2015 10:42:57 +0200 [thread overview]
Message-ID: <55546011.20909@nod.at> (raw)
In-Reply-To: <55545BC8.3010207@huawei.com>
Am 14.05.2015 um 10:24 schrieb Sheng Yong:
>> Isn't this the behavior that all device drivers have?
> Yes, I think so. I just considered that is there any point to do something
> to avoid this, when I read the mail that you suggest Michael to check the
> device node. :-)
We already have a solution for that, udev and devtmpfs.
If you create the nodes by hand you're on your own.
Sadly some embedded folks still do, that's why I was asking...
Thanks,
//richard
next prev parent reply other threads:[~2015-05-14 8:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5552EE30.8060203@gmail.com>
2015-05-13 6:25 ` Cannot mount ubifs partition Michael Niarchos
2015-05-13 6:49 ` Richard Weinberger
2015-05-13 8:48 ` Michael Niarchos
2015-05-13 8:50 ` Richard Weinberger
2015-05-13 8:56 ` Michael Niarchos
2015-05-13 8:59 ` Richard Weinberger
2015-05-13 9:06 ` Michael Niarchos
2015-05-13 9:10 ` Richard Weinberger
2015-05-13 9:27 ` Michael Niarchos
2015-05-13 9:20 ` Richard Weinberger
2015-05-13 9:43 ` Michael Niarchos
2015-05-13 10:16 ` Richard Weinberger
[not found] ` <5553286E.2090303@gmail.com>
[not found] ` <55532AA2.5020808@nod.at>
2015-05-13 10:58 ` Michael Niarchos
2015-05-13 10:59 ` Richard Weinberger
2015-05-13 11:19 ` Michael Niarchos
2015-05-14 3:45 ` Sheng Yong
2015-05-14 7:58 ` Richard Weinberger
2015-05-14 8:24 ` Sheng Yong
2015-05-14 8:42 ` Richard Weinberger [this message]
[not found] <mailman.43705.1431478462.22890.linux-mtd@lists.infradead.org>
2015-05-13 1:57 ` Bean Huo 霍斌斌 (beanhuo)
2015-05-13 6:29 ` Michael Niarchos
2015-05-12 19:38 Michael N
2015-05-13 3:05 ` Brian Norris
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=55546011.20909@nod.at \
--to=richard@nod.at \
--cc=linux-mtd@lists.infradead.org \
--cc=michael.niarchos@gmail.com \
--cc=shengyong1@huawei.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 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.