From: "H. Peter Anvin" <hpa@zytor.com>
To: Satyam Sharma <satyam@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i386 cpuid: Misc cpuinit annotations
Date: Thu, 23 Aug 2007 15:53:13 -0700 [thread overview]
Message-ID: <46CE0FD9.1030008@zytor.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0708230507160.2049@enigma.security.iitk.ac.in>
Satyam Sharma wrote:
> cpuid_class_cpu_callback() is callback function of a CPU hotplug
> notifier_block (that is already marked as __cpuinitdata). Therefore
> it can safely be marked as __cpuinit.
>
> cpuid_device_create() is only referenced from other functions that
> are __cpuinit or __init. So it can also be safely marked __cpuinit.
>
> Signed-off-by: Satyam Sharma <satyam@infradead.org>
Acked-by: H. Peter Anvin <hpa@zytor.com>
> arch/i386/kernel/cpuid.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/arch/i386/kernel/cpuid.c b/arch/i386/kernel/cpuid.c
> index 5c2faa1..a6761fd 100644
> --- a/arch/i386/kernel/cpuid.c
> +++ b/arch/i386/kernel/cpuid.c
> @@ -152,7 +152,7 @@ static const struct file_operations cpuid_fops = {
> .open = cpuid_open,
> };
>
> -static int cpuid_device_create(int i)
> +static int __cpuinit cpuid_device_create(int i)
> {
> int err = 0;
> struct device *dev;
> @@ -163,7 +163,9 @@ static int cpuid_device_create(int i)
> return err;
> }
>
> -static int cpuid_class_cpu_callback(struct notifier_block *nfb, unsigned long action, void *hcpu)
> +static int __cpuinit cpuid_class_cpu_callback(struct notifier_block *nfb,
> + unsigned long action,
> + void *hcpu)
> {
> unsigned int cpu = (unsigned long)hcpu;
>
prev parent reply other threads:[~2007-08-23 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 23:38 [PATCH] i386 cpuid: Misc cpuinit annotations Satyam Sharma
2007-08-23 22:53 ` H. Peter Anvin [this message]
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=46CE0FD9.1030008@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=satyam@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