linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 7/7] arm/arm64: Unexport restart handlers
Date: Mon, 14 Jul 2014 16:09:09 +0100	[thread overview]
Message-ID: <20140714150909.GF1112@arm.com> (raw)
In-Reply-To: <53C3EBAA.9050907@roeck-us.net>

On Mon, Jul 14, 2014 at 03:39:38PM +0100, Guenter Roeck wrote:
> On 07/14/2014 07:22 AM, Catalin Marinas wrote:
> > On Sun, Jul 13, 2014 at 04:30:31PM +0100, Guenter Roeck wrote:
> >> Implementing a restart handler in a module don't make sense
> >> as there would be no guarantee that the module is loaded when
> >> a restart is needed. Unexport arm_pm_restart to ensure that
> >> no one gets the idea to do it anyway.
> >>
> >> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> >> ---
> >> v4: No change
> >> v3: No change
> >> v2: No change
> >>
> >>   arch/arm/kernel/process.c   | 1 -
> >>   arch/arm64/kernel/process.c | 1 -
> >>   2 files changed, 2 deletions(-)
> >>
> >> diff --git a/arch/arm/kernel/process.c b/arch/arm/kernel/process.c
> >> index 5d191e3..25c7f00 100644
> >> --- a/arch/arm/kernel/process.c
> >> +++ b/arch/arm/kernel/process.c
> >> @@ -125,7 +125,6 @@ void (*pm_power_off)(void);
> >>   EXPORT_SYMBOL(pm_power_off);
> >>
> >>   void (*arm_pm_restart)(enum reboot_mode reboot_mode, const char *cmd) = null_restart;
> >> -EXPORT_SYMBOL_GPL(arm_pm_restart);
> >
> > Unless I miss something, how is this different from registering a
> > restart notifier from a module (blocking_notifier_chain_register is
> > exported)?
> 
> A notifier can be unregistered safely, and more than one notifier call
> is supported. If there is more than one driver setting arm_pm_restart,
> the first one to unregister will clear the pointer. Using the notifier
> is cleaner and not architecture dependent. One might argue that setting
> module external function pointers from module code isn't exactly clean
> coding.

I agree.

> Anyway, this patch is not relevant for the series. If you prefer to have
> the function exported, and keep using it for arm drivers loaded as modules,
> be my guest, and I'll be more than happy drop it. I'll take your comment
> as a hint _not_ to convert existing code to use the notifier after the
> series is accepted. Cool, as I hate wasting my time.

No, it's actually the opposite ;) (and I would go further and remove
arm_pm_restart entirely for arm64).

-- 
Catalin

  reply	other threads:[~2014-07-14 15:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-13 15:30 [PATCH v4 0/7] kernel: Add support for restart notifier call chain Guenter Roeck
2014-07-13 15:30 ` [PATCH v4 1/7] " Guenter Roeck
2014-07-14 14:53   ` Catalin Marinas
2014-07-14 14:58     ` Guenter Roeck
2014-07-15 16:12       ` Guenter Roeck
2014-07-13 15:30 ` [PATCH v4 2/7] arm64: Support restart through " Guenter Roeck
2014-07-14 14:55   ` Catalin Marinas
2014-07-14 15:01     ` Guenter Roeck
2014-07-14 15:07       ` Catalin Marinas
2014-07-13 15:30 ` [PATCH v4 3/7] arm: " Guenter Roeck
2014-07-13 15:30 ` [PATCH v4 4/7] power/restart: Call machine_restart instead of arm_pm_restart Guenter Roeck
2014-07-13 15:30 ` [PATCH v4 5/7] watchdog: moxart: Register restart handler with restart notifier Guenter Roeck
2014-07-14 14:19   ` Catalin Marinas
2014-07-14 14:41     ` Guenter Roeck
2014-07-14 15:11       ` Catalin Marinas
2014-07-13 15:30 ` [PATCH v4 6/7] watchdog: alim7101: " Guenter Roeck
2014-07-13 15:30 ` [PATCH v4 7/7] arm/arm64: Unexport restart handlers Guenter Roeck
2014-07-14 14:22   ` Catalin Marinas
2014-07-14 14:39     ` Guenter Roeck
2014-07-14 15:09       ` Catalin Marinas [this message]
2014-07-14 16:26         ` Guenter Roeck

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=20140714150909.GF1112@arm.com \
    --to=catalin.marinas@arm.com \
    --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).