From: Karim Eshapa <karim.eshapa@gmail.com>
To: hubcap@omnibond.com
Cc: linux-kernel@vger.kernel.org, Karim Eshapa <karim.eshapa@gmail.com>
Subject: [PATCH] fs:orangefs:orangefs-debug.h: Use ARRAY_SIZE kernel macro
Date: Thu, 20 Apr 2017 02:59:42 +0200 [thread overview]
Message-ID: <1492649982-15418-1-git-send-email-karim.eshapa@gmail.com> (raw)
Let's use the defined kernel macro more safe
and remove unnecessary cast.
Signed-off-by: Karim Eshapa <karim.eshapa@gmail.com>
---
fs/orangefs/orangefs-debug.h | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/fs/orangefs/orangefs-debug.h b/fs/orangefs/orangefs-debug.h
index 387db17..becd229 100644
--- a/fs/orangefs/orangefs-debug.h
+++ b/fs/orangefs/orangefs-debug.h
@@ -12,6 +12,7 @@
#ifndef __ORANGEFS_DEBUG_H
#define __ORANGEFS_DEBUG_H
+#include "orangefs-kernel.h"
#ifdef __KERNEL__
#include <linux/types.h>
#else
@@ -86,7 +87,7 @@ static struct __keyword_mask_s s_kmod_keyword_mask_map[] = {
{"all", GOSSIP_MAX_DEBUG}
};
-static const int num_kmod_keyword_mask_map = (int)
- (sizeof(s_kmod_keyword_mask_map) / sizeof(struct __keyword_mask_s));
+static const int num_kmod_keyword_mask_map = ARRAY_SIZE(
+ s_kmod_keyword_mask_map);
#endif /* __ORANGEFS_DEBUG_H */
--
2.7.4
next reply other threads:[~2017-04-20 0:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 0:59 Karim Eshapa [this message]
2017-04-20 5:07 ` [PATCH] fs:orangefs:orangefs-debug.h: Use ARRAY_SIZE kernel macro kbuild test robot
2017-04-20 13:04 ` [PATCH] fs:orangefs:orangefs-debug, orangefs-kernel: Fixing warning issues and use ARRAY_SIZE Karim Eshapa
2017-04-20 17:20 ` kbuild test robot
2017-04-20 17:25 ` kbuild test robot
2017-04-20 7:17 ` [PATCH] fs:orangefs:orangefs-debug.h: Use ARRAY_SIZE kernel macro kbuild test robot
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=1492649982-15418-1-git-send-email-karim.eshapa@gmail.com \
--to=karim.eshapa@gmail.com \
--cc=hubcap@omnibond.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;
as well as URLs for NNTP newsgroup(s).