kdb: code cleanup to use macro instead of value
authorJovi Zhang <bookjovi@gmail.com>
Mon, 15 Mar 2010 12:28:00 +0000 (07:28 -0500)
committerJason Wessel <jason.wessel@windriver.com>
Fri, 25 Mar 2011 21:37:30 +0000 (16:37 -0500)
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

index bd3e8e29caa37e3861a6832fd0614a0bd6d5dab4..38a85428c70f33dafeb6aa9e300d356b425f0e8a 100644 (file)
@@ -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;                                    \
This page took 0.044806 seconds and 5 git commands to generate.