From: Jason Wessel <jason.wessel@windriver.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
kgdb-bugreport@lists.sourceforge.net,
Jovi Zhang <bookjovi@gmail.com>,
Jason Wessel <jason.wessel@windriver.com>
Subject: [PATCH 2/4] kdb: code cleanup to use macro instead of value
Date: Fri, 25 Mar 2011 16:44:18 -0500 [thread overview]
Message-ID: <1301089460-1936-3-git-send-email-jason.wessel@windriver.com> (raw)
In-Reply-To: <1301089460-1936-1-git-send-email-jason.wessel@windriver.com>
From: Jovi Zhang <bookjovi@gmail.com>
It's better to use macro KDB_BASE_CMD_MAX instead of 50
Signed-off-by: Jovi Zhang <bookjovi@gmail.com>
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
---
kernel/debug/kdb/kdb_main.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/debug/kdb/kdb_main.c b/kernel/debug/kdb/kdb_main.c
index bd3e8e2..38a8542 100644
--- a/kernel/debug/kdb/kdb_main.c
+++ b/kernel/debug/kdb/kdb_main.c
@@ -78,7 +78,7 @@ static unsigned int kdb_continue_catastrophic;
static kdbtab_t *kdb_commands;
#define KDB_BASE_CMD_MAX 50
static int kdb_max_commands = KDB_BASE_CMD_MAX;
-static kdbtab_t kdb_base_commands[50];
+static kdbtab_t kdb_base_commands[KDB_BASE_CMD_MAX];
#define for_each_kdbcmd(cmd, num) \
for ((cmd) = kdb_base_commands, (num) = 0; \
num < kdb_max_commands; \
--
1.7.1
next prev parent reply other threads:[~2011-03-25 21:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-25 21:44 [GIT PULL] kgdb/kdb tree for 2.6.39-rc1 Jason Wessel
2011-03-25 21:44 ` [PATCH 1/4] kgdboc,kgdbts: strlen() doesn't count the terminator Jason Wessel
2011-03-25 21:44 ` Jason Wessel [this message]
2011-03-25 21:44 ` [PATCH 3/4] kgdb,x86_64: fix compile warning found with sparse Jason Wessel
2011-03-25 21:44 ` [PATCH 4/4] kdb: add usage string of 'per_cpu' command Jason Wessel
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=1301089460-1936-3-git-send-email-jason.wessel@windriver.com \
--to=jason.wessel@windriver.com \
--cc=bookjovi@gmail.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®