From: Brent Pappas <pappasbrent@knights.ucf.edu>
To: Nam Cao <namcaov@gmail.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"cai.huoqing@linux.dev" <cai.huoqing@linux.dev>,
"kuba@kernel.org" <kuba@kernel.org>,
"linux-staging@lists.linux.dev" <linux-staging@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [PATCH v2] staging: most: net: Replace macros HB and LB with static inline functions
Date: Thu, 6 Oct 2022 13:02:34 -0400 [thread overview]
Message-ID: <Yz8KKkZ18svZdeec@knights.ucf.edu> (raw)
In-Reply-To: <20221006134230.GA14040@nam-dell>
Replace function-like macros "HB" and "LB" with static inline functions
to comply with preferred Linux coding style standards.
Signed-off-by: Brent Pappas <pappasbrent@knights.ucf.edu>
---
Changelog:
V1 -> V2: Resent diff from a mail client that would not replace tabs
with spaces so that patch can be successfully applied.
diff --git a/drivers/staging/most/net/net.c b/drivers/staging/most/net/net.c
index 1d1fe8bff7ee..8a8fbc274b73 100644
--- a/drivers/staging/most/net/net.c
+++ b/drivers/staging/most/net/net.c
@@ -36,8 +36,8 @@
#define PMS_TELID_MASK 0x0F
#define PMS_TELID_SHIFT 4
-#define HB(value) ((u8)((u16)(value) >> 8))
-#define LB(value) ((u8)(value))
+static inline u8 HB(unsigned int value) { return ((u8)((u16)(value) >> 8)); }
+static inline u8 LB(unsigned int value) { return ((u8)(value)); }
#define EXTRACT_BIT_SET(bitset_name, value) \
(((value) >> bitset_name##_SHIFT) & bitset_name##_MASK)
next prev parent reply other threads:[~2022-10-06 17:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 16:10 [PATCH] staging: most: net: Replace macros HB and LB with static inline functions Brent Pappas
2022-10-05 23:57 ` Nam Cao
2022-10-06 1:39 ` Brent Pappas
2022-10-06 13:21 ` Brent Pappas
2022-10-06 13:42 ` Nam Cao
2022-10-06 17:02 ` Brent Pappas [this message]
2022-10-06 17:44 ` [PATCH v2] " Nam Cao
2022-10-06 23:07 ` [PATCH v3] " Brent Pappas
2022-10-20 15:25 ` Greg KH
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=Yz8KKkZ18svZdeec@knights.ucf.edu \
--to=pappasbrent@knights.ucf.edu \
--cc=cai.huoqing@linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=namcaov@gmail.com \
/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