From: Adrian Bunk <bunk@kernel.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: linux-kernel@vger.kernel.org, len.brown@intel.com,
Andi Kleen <ak@suse.de>
Subject: Re: [PATCH 1/4] introduce __cpuinitconst
Date: Fri, 11 Jan 2008 23:00:44 +0200 [thread overview]
Message-ID: <20080111210044.GA17276@does.not.exist> (raw)
In-Reply-To: <47873D40.76E4.0078.0@novell.com>
On Fri, Jan 11, 2008 at 08:56:16AM +0000, Jan Beulich wrote:
> The patch doesn't change all instances where 'const' could have been
> added as a result of the base structure changes, only where the change
> has a real effect (the module loader doesn't enforce read-only section
> attributes at present, so only built-in files make a real difference).
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
> Cc: Len Brown <len.brown@intel.com>
> Cc: Andi Kleen <ak@suse.de>
>
> ---
> drivers/acpi/processor_idle.c | 2 +-
> include/linux/init.h | 2 ++
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> --- 2.6.24-rc7-initconst.orig/drivers/acpi/processor_idle.c
> +++ 2.6.24-rc7-initconst/drivers/acpi/processor_idle.c
> @@ -118,7 +118,7 @@ static int set_max_cstate(const struct d
>
> /* Actually this shouldn't be __cpuinitdata, would be better to fix the
> callers to only run once -AK */
> -static struct dmi_system_id __cpuinitdata processor_power_dmi_table[] = {
> +static struct dmi_system_id __cpuinitconst processor_power_dmi_table[] = {
> { set_max_cstate, "IBM ThinkPad R40e", {
> DMI_MATCH(DMI_BIOS_VENDOR,"IBM"),
> DMI_MATCH(DMI_BIOS_VERSION,"1SET70WW")}, (void *)1},
> --- 2.6.24-rc7-initconst.orig/include/linux/init.h
> +++ 2.6.24-rc7-initconst/include/linux/init.h
> @@ -269,11 +269,13 @@ void __init parse_early_param(void);
> #ifdef CONFIG_HOTPLUG_CPU
> #define __cpuinit
> #define __cpuinitdata
> +#define __cpuinitconst const
> #define __cpuexit
> #define __cpuexitdata
> #else
> #define __cpuinit __init
> #define __cpuinitdata __initdata
> +#define __cpuinitconst __initdata
> #define __cpuexit __exit
> #define __cpuexitdata __exitdata
> #endif
__cpuinitconstdata ?
I know it's a bit long, but it would be more logically when looking at
the other ones.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-01-11 21:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 8:56 [PATCH 1/4] introduce __cpuinitconst Jan Beulich
2008-01-11 21:00 ` Adrian Bunk [this message]
2008-01-14 8:12 ` Jan Beulich
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=20080111210044.GA17276@does.not.exist \
--to=bunk@kernel.org \
--cc=ak@suse.de \
--cc=jbeulich@novell.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.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.