From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: cpufreq: mediatek: allow modular build
Date: Fri, 11 Sep 2015 14:08:06 +0530 [thread overview]
Message-ID: <20150911083806.GM9650@linux> (raw)
In-Reply-To: <3071823.f1VzTWVMmV@wuerfel>
On 11-09-15, 10:36, Arnd Bergmann wrote:
> I don't consider that a bug: a module with just an init function and
> no exit function can be loaded once and never unloaded, which is not
> nice for debugging, but is otherwise fully functional.
For me, there are two essential things that a module has to support:
- hotplug, which is just fine.
- hot-unplug, which will pass as well, but without freeing resources..
:)
--
viresh
WARNING: multiple messages have this Message-ID (diff)
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Pi-Cheng Chen <pi-cheng.chen@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: cpufreq: mediatek: allow modular build
Date: Fri, 11 Sep 2015 14:08:06 +0530 [thread overview]
Message-ID: <20150911083806.GM9650@linux> (raw)
In-Reply-To: <3071823.f1VzTWVMmV@wuerfel>
On 11-09-15, 10:36, Arnd Bergmann wrote:
> I don't consider that a bug: a module with just an init function and
> no exit function can be loaded once and never unloaded, which is not
> nice for debugging, but is otherwise fully functional.
For me, there are two essential things that a module has to support:
- hotplug, which is just fine.
- hot-unplug, which will pass as well, but without freeing resources..
:)
--
viresh
next prev parent reply other threads:[~2015-09-11 8:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 8:15 cpufreq: mediatek: allow modular build Arnd Bergmann
2015-09-11 8:15 ` Arnd Bergmann
2015-09-11 8:17 ` Viresh Kumar
2015-09-11 8:17 ` Viresh Kumar
2015-09-11 8:22 ` Arnd Bergmann
2015-09-11 8:22 ` Arnd Bergmann
2015-09-11 8:25 ` Viresh Kumar
2015-09-11 8:25 ` Viresh Kumar
2015-09-11 8:36 ` Arnd Bergmann
2015-09-11 8:36 ` Arnd Bergmann
2015-09-11 8:38 ` Viresh Kumar [this message]
2015-09-11 8:38 ` Viresh Kumar
2015-09-11 9:34 ` Russell King - ARM Linux
2015-09-11 9:34 ` Russell King - ARM Linux
2015-09-11 9:40 ` Viresh Kumar
2015-09-11 9:40 ` Viresh Kumar
2015-09-11 9:58 ` Russell King - ARM Linux
2015-09-11 9:58 ` Russell King - ARM Linux
2015-09-11 10:09 ` Viresh Kumar
2015-09-11 10:09 ` Viresh Kumar
2015-09-11 10:13 ` Russell King - ARM Linux
2015-09-11 10:13 ` Russell King - ARM Linux
2015-09-11 10:19 ` Viresh Kumar
2015-09-11 10:19 ` Viresh Kumar
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=20150911083806.GM9650@linux \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@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 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.