From: Artem Bityutskiy <dedekind1@gmail.com>
To: Lee Amirev <lee.amirev@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: To remove UBI Control Device . . .
Date: Thu, 04 Feb 2010 07:09:25 +0200 [thread overview]
Message-ID: <1265260166.2517.39.camel@localhost.localdomain> (raw)
In-Reply-To: <e14c53d91001251215k5e7074d4lb579d43df530b94a@mail.gmail.com>
On Mon, 2010-01-25 at 15:15 -0500, Lee Amirev wrote:
> My system does not need to dynamically attach or detach MTD devices to
> UBI. We can just attach all that we need through boot or module
> parameters. Therefore, we don't need the UBI control device
> (/dev/ubi_ctrl). In order to prevent the device from existing, I
> could simply comment out the misc_register and misc_deregister calls
> in ubi_init or ubi_exit in /drivers/mtd/ubi/build.c. Is this
> sufficient? Are there any unintended consequences in removing the
> control device?
It should be fine. But I do not think it is nice solution. I think the
proper solution is to amend your udev rules.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-02-04 5:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 20:15 To remove UBI Control Device . . Lee Amirev
2010-02-04 5:09 ` Artem Bityutskiy [this message]
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=1265260166.2517.39.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=lee.amirev@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