From: "Ken O'Brien" <kernel@kenobrien.org>
To: gregkh@linuxfoundation.org
Cc: swetland@google.com, arve@android.com, viro@zeniv.linux.org.uk,
dhowells@redhat.com, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org,
"Ken O'Brien" <kernel@kenobrien.org>
Subject: [PATCH 2/2] staging: android: binder.c: checkpatch.pl
Date: Sat, 20 Oct 2012 23:33:20 +0100 [thread overview]
Message-ID: <1350772400-12347-2-git-send-email-kernel@kenobrien.org> (raw)
In-Reply-To: <1350772400-12347-1-git-send-email-kernel@kenobrien.org>
Fixed 3 instances of "WARNING: static const char * array should probably be static const char * const" warnings from checkpatch
Signed-off-by: Ken O'Brien <kernel@kenobrien.org>
---
drivers/staging/android/binder.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/android/binder.c b/drivers/staging/android/binder.c
index 8607628..b17f9ba 100644
--- a/drivers/staging/android/binder.c
+++ b/drivers/staging/android/binder.c
@@ -3218,7 +3218,7 @@ static void print_binder_proc(struct seq_file *m,
m->count = start_pos;
}
-static const char *binder_return_strings[] = {
+static const char *const binder_return_strings[] = {
"BR_ERROR",
"BR_OK",
"BR_TRANSACTION",
@@ -3239,7 +3239,7 @@ static const char *binder_return_strings[] = {
"BR_FAILED_REPLY"
};
-static const char *binder_command_strings[] = {
+static const char *const binder_command_strings[] = {
"BC_TRANSACTION",
"BC_REPLY",
"BC_ACQUIRE_RESULT",
@@ -3259,7 +3259,7 @@ static const char *binder_command_strings[] = {
"BC_DEAD_BINDER_DONE"
};
-static const char *binder_objstat_strings[] = {
+static const char *const binder_objstat_strings[] = {
"proc",
"thread",
"node",
--
1.7.12.4
next prev parent reply other threads:[~2012-10-20 22:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-20 22:33 [PATCH 1/2] staging: android: checkpatch.pl fixes Ken O'Brien
2012-10-20 22:33 ` Ken O'Brien [this message]
2012-10-21 1:05 ` Joe Perches
2012-10-21 2:05 ` Cruz Julian Bishop
2012-10-21 2:09 ` Joe Perches
2012-10-22 9:37 ` David Howells
2012-10-22 12:15 ` Joe Perches
2012-10-22 13:02 ` Peter Hurley
2012-10-22 13:16 ` [PATCH] checkpatch: Warn on unnecessary line continuations Joe Perches
2012-10-22 16:45 ` Joe Perches
2012-10-28 4:46 ` [PATCH v2] " Joe Perches
2012-10-22 20:03 ` [PATCH 1/2] staging: android: checkpatch.pl fixes Greg KH
2012-10-24 14:48 ` kernel kernel
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=1350772400-12347-2-git-send-email-kernel@kenobrien.org \
--to=kernel@kenobrien.org \
--cc=arve@android.com \
--cc=devel@driverdev.osuosl.org \
--cc=dhowells@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swetland@google.com \
--cc=viro@zeniv.linux.org.uk \
/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