From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Arnd Bergmann" <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org,
"Dong Aisheng" <dong.aisheng@linaro.org>,
"Samuel Ortiz" <sameo@linux.intel.com>,
"Mark Brown" <broonie@opensource.wolfsonmicro.com>
Subject: Re[2]: [PATCH v2 1/3] mfd: syscon: Removed support for unloading
Date: Tue, 12 Feb 2013 10:35:35 +0400 [thread overview]
Message-ID: <1360650935.475602112@f368.mail.ru> (raw)
In-Reply-To: <201302112005.35034.arnd@arndb.de>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 799 bytes --]
Hello.
> On Monday 11 February 2013, 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.
> >
> > Signed-off-by: Alexander Shiyan <shc_work@mail.ru>
>
> Can you describe a scenario where that would happen? Normally the
> module should stay pinned as long as any other module refers
> to its exported symbols.
Probably I wrote a bad description.
The driver registered by "postcore_initcall". Therefore, if we unregister the
driver, we have no way to register it back. Fixme please.
---
ÿôèº{.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-12 6:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 18:42 [PATCH v2 1/3] mfd: syscon: Removed support for unloading Alexander Shiyan
2013-02-11 18:42 ` [PATCH v2 2/3] mfd: syscon: Removed unneeded field "dev" from private driver structure Alexander Shiyan
2013-02-17 2:57 ` Dong Aisheng
2013-02-11 18:42 ` [PATCH v2 3/3] mfd: syscon: Add non-DT support Alexander Shiyan
2013-02-11 20:05 ` [PATCH v2 1/3] mfd: syscon: Removed support for unloading Arnd Bergmann
2013-02-12 6:35 ` Alexander Shiyan [this message]
2013-02-12 11:38 ` Re[2]: " Arnd Bergmann
2013-02-17 2:42 ` Dong Aisheng
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=1360650935.475602112@f368.mail.ru \
--to=shc_work@mail.ru \
--cc=arnd@arndb.de \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dong.aisheng@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox