From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Stephen Warren" <swarren@wwwdotorg.org>
Cc: linux-kernel@vger.kernel.org, "Arnd Bergmann" <arnd@arndb.de>,
"Dong Aisheng" <dong.aisheng@linaro.org>,
"Samuel Ortiz" <sameo@linux.intel.com>,
"Mark Brown" <broonie@opensource.wolfsonmicro.com>,
"Thierry Reding" <thierry.reding@avionic-design.de>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re[2]: [PATCH v5 1/3] mfd: syscon: Removed support for unloading
Date: Sat, 23 Feb 2013 09:28:28 +0400 [thread overview]
Message-ID: <1361597308.137178281@f2.mail.ru> (raw)
In-Reply-To: <512851E0.7000808@wwwdotorg.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 742 bytes --]
> On 02/22/2013 10:15 PM, Alexander Shiyan wrote:
> > The driver can be used in various subsystems and therefore should not
> > be unloaded when it is defined in the kernel configuration, so remove
> > support for unloading it.
>
> Why not fix the clients to module_get() at the appropriate times; then
> you could still allow unloading, couldn't you?
I has explain this before. Driver defined as "bool" and loaded via postcore_initcall.
Once loaded it should not be unloaded, in other case it have not way to be loaded back.
I am correctly understand your question?
Thanks.
---
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2013-02-23 5:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-23 5:15 Alexander Shiyan
2013-02-23 5:15 ` [PATCH v5 2/3] mfd: syscon: Removed unneeded field "dev" from private driver structure Alexander Shiyan
2013-02-23 5:15 ` [PATCH v5 3/3] mfd: syscon: Add non-DT support Alexander Shiyan
2013-02-23 5:21 ` [PATCH v5 1/3] mfd: syscon: Removed support for unloading Stephen Warren
2013-02-23 5:28 ` Alexander Shiyan [this message]
2013-02-23 23:51 ` Stephen Warren
2013-02-24 7:55 ` Dmitry Torokhov
2013-02-25 6:53 ` Re[2]: " Alexander Shiyan
2013-02-25 7:07 ` Dmitry Torokhov
2013-02-23 22:17 ` Arnd Bergmann
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=1361597308.137178281@f2.mail.ru \
--to=shc_work@mail.ru \
--cc=arnd@arndb.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dong.aisheng@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@avionic-design.de \
/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
Powered by JetHome