From: tip-bot for Greg Dietsche <Gregory.Dietsche@cuw.edu>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
Gregory.Dietsche@cuw.edu, tglx@linutronix.de,
hpa@linux.intel.com
Subject: [tip:x86/cleanups] x86, smpboot: Mark names[] array as const
Date: Fri, 1 Jul 2011 00:21:59 GMT [thread overview]
Message-ID: <tip-a5fd117a8fda8621e1ae1bb3b8d55e4c0ebabd94@git.kernel.org> (raw)
In-Reply-To: <1309473108-5337-1-git-send-email-Gregory.Dietsche@cuw.edu>
Commit-ID: a5fd117a8fda8621e1ae1bb3b8d55e4c0ebabd94
Gitweb: http://git.kernel.org/tip/a5fd117a8fda8621e1ae1bb3b8d55e4c0ebabd94
Author: Greg Dietsche <Gregory.Dietsche@cuw.edu>
AuthorDate: Thu, 30 Jun 2011 17:31:48 -0500
Committer: H. Peter Anvin <hpa@linux.intel.com>
CommitDate: Thu, 30 Jun 2011 16:44:12 -0700
x86, smpboot: Mark names[] array as const
The array names[] in __inquire_remote_apic is read-only. Make it
explicit by marking as const.
Signed-off-by: Greg Dietsche <Gregory.Dietsche@cuw.edu>
Link: http://lkml.kernel.org/r/1309473108-5337-1-git-send-email-Gregory.Dietsche@cuw.edu
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
---
arch/x86/kernel/smpboot.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/smpboot.c b/arch/x86/kernel/smpboot.c
index a3c430b..4dbf60e 100644
--- a/arch/x86/kernel/smpboot.c
+++ b/arch/x86/kernel/smpboot.c
@@ -425,7 +425,7 @@ static void impress_friends(void)
void __inquire_remote_apic(int apicid)
{
unsigned i, regs[] = { APIC_ID >> 4, APIC_LVR >> 4, APIC_SPIV >> 4 };
- char *names[] = { "ID", "VERSION", "SPIV" };
+ const char const *names[] = { "ID", "VERSION", "SPIV" };
int timeout;
u32 status;
next parent reply other threads:[~2011-07-01 0:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1309473108-5337-1-git-send-email-Gregory.Dietsche@cuw.edu>
2011-07-01 0:21 ` tip-bot for Greg Dietsche [this message]
2011-07-01 0:25 ` [tip:x86/cleanups] x86, smpboot: Mark names[] array as const H. Peter Anvin
2011-07-01 0:41 ` Greg Dietsche
2011-07-01 0:47 ` H. Peter Anvin
2011-07-01 1:20 ` Brian Gerst
2011-07-01 1:21 ` H. Peter Anvin
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=tip-a5fd117a8fda8621e1ae1bb3b8d55e4c0ebabd94@git.kernel.org \
--to=gregory.dietsche@cuw.edu \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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