From: "Edward O'Callaghan" <eocallaghan@alterapraxis.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] arch/x86/kernel/rtc.c: Overzealous usage of 'const' keyword
Date: Sun, 12 Oct 2014 22:53:43 +1100 [thread overview]
Message-ID: <20141012225343.0bb95e1c.eocallaghan@alterapraxis.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 403 bytes --]
Please merge.
--
______________________________________________________________________
Edward O'Callaghan, Director and Principal consultant.
https://www.alterapraxis.com | eocallaghan@alterapraxis.com
Altera Praxis Pty Ltd, // Discretions in cybersecurity
ACN 165 424 064. // reconnaissance and adversary mitigation.
______________________________________________________________________
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-arch-x86-kernel-rtc.c-Overzealous-usage-of-const-key.patch --]
[-- Type: text/x-patch, Size: 1020 bytes --]
From f8847c4eb8f7550c43e2dbc9efaff91434a54fe7 Mon Sep 17 00:00:00 2001
From: Edward O'Callaghan <eocallaghan@alterapraxis.com>
Date: Sun, 12 Oct 2014 22:25:40 +1100
Subject: [PATCH] arch/x86/kernel/rtc.c: Overzealous usage of 'const' keyword
Organization: Altera Praxis Pty Ltd.
To: linux-kernel@vger.kernel.org
No need to qualify with 'const' no less than three times over.
Signed-off-by: Edward O'Callaghan <eocallaghan@alterapraxis.com>
---
arch/x86/kernel/rtc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/rtc.c b/arch/x86/kernel/rtc.c
index ca9622a..75cf16a 100644
--- a/arch/x86/kernel/rtc.c
+++ b/arch/x86/kernel/rtc.c
@@ -170,7 +170,7 @@ static struct platform_device rtc_device = {
static __init int add_rtc_cmos(void)
{
#ifdef CONFIG_PNP
- static const char * const const ids[] __initconst =
+ static const char * ids[] __initconst =
{ "PNP0b00", "PNP0b01", "PNP0b02", };
struct pnp_dev *dev;
struct pnp_id *id;
--
2.1.2
reply other threads:[~2014-10-12 11:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141012225343.0bb95e1c.eocallaghan@alterapraxis.com \
--to=eocallaghan@alterapraxis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®