linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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 15:39:16 +0530	[thread overview]
Message-ID: <20150911100916.GO9650@linux> (raw)
In-Reply-To: <20150911095820.GM21084@n2100.arm.linux.org.uk>

On 11-09-15, 10:58, Russell King - ARM Linux wrote:
> Not module "unplug" (I've never heard it called that before).  A module
> with a module_init() but no module_exit() can only be added to a running
> kernel, and never removed.  That's intentional behaviour.

Ah, I see. I wasn't sure that a module with no module_exit() can't be
removed.

> However, if you're talking about hot-unplug, presumably you're talking
> about _CPU_ hot-unplug, and that's something the code should definitely
> handle irrespective of whether it's built-in or a module.
> 
> The two issues are entirely separate.

Bah, all this time I meant module insertion/removal, sorry :(

-- 
viresh

  reply	other threads:[~2015-09-11 10:09 UTC|newest]

Thread overview: 12+ 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:17 ` Viresh Kumar
2015-09-11  8:22   ` Arnd Bergmann
2015-09-11  8:25     ` Viresh Kumar
2015-09-11  8:36       ` Arnd Bergmann
2015-09-11  8:38         ` Viresh Kumar
2015-09-11  9:34           ` Russell King - ARM Linux
2015-09-11  9:40             ` Viresh Kumar
2015-09-11  9:58               ` Russell King - ARM Linux
2015-09-11 10:09                 ` Viresh Kumar [this message]
2015-09-11 10:13                   ` Russell King - ARM Linux
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=20150911100916.GO9650@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).