From: Darren Hart <dvhart@infradead.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: andy@infradead.org, platform-driver-x86@vger.kernel.org,
akpm@linux-foundation.org, Andi Kleen <ak@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org
Subject: Re: [PATCH] Fix const confusion in intel-mid x86 platform drivers
Date: Thu, 21 Dec 2017 18:08:35 -0800 [thread overview]
Message-ID: <20171222020835.GA17014@fury> (raw)
In-Reply-To: <20171222001443.2067-1-andi@firstfloor.org>
On Thu, Dec 21, 2017 at 04:14:43PM -0800, Andi Kleen wrote:
> From: Andi Kleen <ak@linux.intel.com>
>
> const must be marked __initconst, not __initdata
>
Thanks Andi,
This file should go through the x86 maintainers per the current MAINTAINERS
file. So to avoid risk of duplication, added Thomas et al. to Cc.
Thomas, we discussed moving more of arch/x86/platform to drivers/platform/x86.
We have migrated pmc_atom already, but a lot remains. Do you want to pull
patches like this in the interim, or should we move arch/x86/platform under
our entry in MAINTAINERS now?
Reviewed-by: Darren Hart (VMware) <dvhart@infradead.org>
> Signed-off-by: Andi Kleen <ak@linux.intel.com>
> ---
> arch/x86/platform/intel-mid/device_libs/platform_bt.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/x86/platform/intel-mid/device_libs/platform_bt.c b/arch/x86/platform/intel-mid/device_libs/platform_bt.c
> index dc036e511f48..2b5d86ce24c2 100644
> --- a/arch/x86/platform/intel-mid/device_libs/platform_bt.c
> +++ b/arch/x86/platform/intel-mid/device_libs/platform_bt.c
> @@ -60,7 +60,7 @@ static int __init tng_bt_sfi_setup(struct bt_sfi_data *ddata)
> return 0;
> }
>
> -static const struct bt_sfi_data tng_bt_sfi_data __initdata = {
> +static const struct bt_sfi_data tng_bt_sfi_data __initconst = {
> .setup = tng_bt_sfi_setup,
> };
>
> --
> 2.15.0
>
>
--
Darren Hart
VMware Open Source Technology Center
next prev parent reply other threads:[~2017-12-22 2:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 0:14 [PATCH] Fix const confusion in intel-mid x86 platform drivers Andi Kleen
2017-12-22 2:08 ` Darren Hart [this message]
2017-12-28 9:47 ` Andy Shevchenko
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=20171222020835.GA17014@fury \
--to=dvhart@infradead.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=andy@infradead.org \
--cc=hpa@zytor.com \
--cc=mingo@elte.hu \
--cc=platform-driver-x86@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@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.