Messages in this thread Patch in this message | | | Date | Wed, 21 Mar 2007 19:27:34 -0700 | From | Randy Dunlap <> | Subject | [PATCH -mm] nozomi: use NULL for pointers |
| |
From: Randy Dunlap <randy.dunlap@oracle.com>
Use NULL instead of 0 for pointers: drivers/char/nozomi.c:1028:68: warning: Using plain integer as NULL pointer drivers/char/nozomi.c:1029:68: warning: Using plain integer as NULL pointer drivers/char/nozomi.c:1031:68: warning: Using plain integer as NULL pointer drivers/char/nozomi.c:1032:68: warning: Using plain integer as NULL pointer drivers/char/nozomi.c:1034:70: warning: Using plain integer as NULL pointer drivers/char/nozomi.c:1035:70: warning: Using plain integer as NULL pointer drivers/char/nozomi.c:1037:68: warning: Using plain integer as NULL pointer drivers/char/nozomi.c:1039:68: warning: Using plain integer as NULL pointer drivers/char/nozomi.c:1040:68: warning: Using plain integer as NULL pointer drivers/char/nozomi.c:1042:68: warning: Using plain integer as NULL pointer drivers/char/nozomi.c:1043:68: warning: Using plain integer as NULL pointer drivers/char/nozomi.c:1045:68: warning: Using plain integer as NULL pointer drivers/char/nozomi.c:1046:68: warning: Using plain integer as NULL pointer drivers/char/nozomi.c:1048:64: warning: Using plain integer as NULL pointer
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com> --- drivers/char/nozomi.c | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-)
--- linux-2.6.21-rc4-mm1.orig/drivers/char/nozomi.c +++ linux-2.6.21-rc4-mm1/drivers/char/nozomi.c @@ -1025,27 +1025,27 @@ static char *interrupt2str(u16 interrupt static char buf[TMP_BUF_MAX]; char *p = buf; - interrupt & MDM_DL1 ? p += snprintf(p, TMP_BUF_MAX, "MDM_DL1 ") : 0; - interrupt & MDM_DL2 ? p += snprintf(p, TMP_BUF_MAX, "MDM_DL2 ") : 0; + interrupt & MDM_DL1 ? p += snprintf(p, TMP_BUF_MAX, "MDM_DL1 ") : NULL; + interrupt & MDM_DL2 ? p += snprintf(p, TMP_BUF_MAX, "MDM_DL2 ") : NULL; - interrupt & MDM_UL1 ? p += snprintf(p, TMP_BUF_MAX, "MDM_UL1 ") : 0; - interrupt & MDM_UL2 ? p += snprintf(p, TMP_BUF_MAX, "MDM_UL2 ") : 0; + interrupt & MDM_UL1 ? p += snprintf(p, TMP_BUF_MAX, "MDM_UL1 ") : NULL; + interrupt & MDM_UL2 ? p += snprintf(p, TMP_BUF_MAX, "MDM_UL2 ") : NULL; - interrupt & DIAG_DL1 ? p += snprintf(p, TMP_BUF_MAX, "DIAG_DL1 ") : 0; - interrupt & DIAG_DL2 ? p += snprintf(p, TMP_BUF_MAX, "DIAG_DL2 ") : 0; + interrupt & DIAG_DL1 ? p += snprintf(p, TMP_BUF_MAX, "DIAG_DL1 ") : NULL; + interrupt & DIAG_DL2 ? p += snprintf(p, TMP_BUF_MAX, "DIAG_DL2 ") : NULL; - interrupt & DIAG_UL ? p += snprintf(p, TMP_BUF_MAX, "DIAG_UL ") : 0; + interrupt & DIAG_UL ? p += snprintf(p, TMP_BUF_MAX, "DIAG_UL ") : NULL; - interrupt & APP1_DL ? p += snprintf(p, TMP_BUF_MAX, "APP1_DL ") : 0; - interrupt & APP2_DL ? p += snprintf(p, TMP_BUF_MAX, "APP2_DL ") : 0; + interrupt & APP1_DL ? p += snprintf(p, TMP_BUF_MAX, "APP1_DL ") : NULL; + interrupt & APP2_DL ? p += snprintf(p, TMP_BUF_MAX, "APP2_DL ") : NULL; - interrupt & APP1_UL ? p += snprintf(p, TMP_BUF_MAX, "APP1_UL ") : 0; - interrupt & APP2_UL ? p += snprintf(p, TMP_BUF_MAX, "APP2_UL ") : 0; + interrupt & APP1_UL ? p += snprintf(p, TMP_BUF_MAX, "APP1_UL ") : NULL; + interrupt & APP2_UL ? p += snprintf(p, TMP_BUF_MAX, "APP2_UL ") : NULL; - interrupt & CTRL_DL ? p += snprintf(p, TMP_BUF_MAX, "CTRL_DL ") : 0; - interrupt & CTRL_UL ? p += snprintf(p, TMP_BUF_MAX, "CTRL_UL ") : 0; + interrupt & CTRL_DL ? p += snprintf(p, TMP_BUF_MAX, "CTRL_DL ") : NULL; + interrupt & CTRL_UL ? p += snprintf(p, TMP_BUF_MAX, "CTRL_UL ") : NULL; - interrupt & RESET ? p += snprintf(p, TMP_BUF_MAX, "RESET ") : 0; + interrupt & RESET ? p += snprintf(p, TMP_BUF_MAX, "RESET ") : NULL; return buf; } - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |