From: zhong jiang <zhongjiang@huawei.com>
To: <davem@davemloft.net>
Cc: <ubraun@linux.ibm.com>, <jwi@linux.ibm.com>, <jhs@mojatatu.com>,
<xiyou.wangcong@gmail.com>, <Ariel.Elior@cavium.com>,
<everest-linux-l2@cavium.com>, <grygorii.strashko@ti.com>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<borntraeger@de.ibm.com>
Subject: [RESEND PATCH 4/5] net: qede: Use FIELD_SIZEOF directly instead of reimplementing its function
Date: Wed, 19 Sep 2018 19:32:13 +0800 [thread overview]
Message-ID: <1537356734-51676-5-git-send-email-zhongjiang@huawei.com> (raw)
In-Reply-To: <1537356734-51676-1-git-send-email-zhongjiang@huawei.com>
FIELD_SIZEOF is defined as a macro to calculate the specified value. Therefore,
We prefer to use the macro rather than calculating its value.
Signed-off-by: zhong jiang <zhongjiang@huawei.com>
---
drivers/net/ethernet/qlogic/qede/qede.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/qlogic/qede/qede.h b/drivers/net/ethernet/qlogic/qede/qede.h
index 6a4d266..de98a97 100644
--- a/drivers/net/ethernet/qlogic/qede/qede.h
+++ b/drivers/net/ethernet/qlogic/qede/qede.h
@@ -440,7 +440,7 @@ struct qede_fastpath {
struct qede_tx_queue *txq;
struct qede_tx_queue *xdp_tx;
-#define VEC_NAME_SIZE (sizeof(((struct net_device *)0)->name) + 8)
+#define VEC_NAME_SIZE (FIELD_SIZEOF(struct net_device, name) + 8)
char name[VEC_NAME_SIZE];
};
--
1.7.12.4
next prev parent reply other threads:[~2018-09-19 11:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 11:32 [RESEND PATCH 0/5] net: Use FIELD_SIZEOF directly instead of reimplementing its function zhong jiang
2018-09-19 11:32 ` [RESEND PATCH 1/5] net: iucv: " zhong jiang
2018-09-19 11:32 ` [RESEND PATCH 2/5] net: sched: " zhong jiang
2018-09-19 11:32 ` [RESEND PATCH 3/5] net: core: " zhong jiang
2018-09-19 11:32 ` zhong jiang [this message]
2018-09-19 11:32 ` [RESEND PATCH 5/5] net: ti: " zhong jiang
2018-09-20 3:58 ` [RESEND PATCH 0/5] net: " David Miller
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=1537356734-51676-5-git-send-email-zhongjiang@huawei.com \
--to=zhongjiang@huawei.com \
--cc=Ariel.Elior@cavium.com \
--cc=borntraeger@de.ibm.com \
--cc=davem@davemloft.net \
--cc=everest-linux-l2@cavium.com \
--cc=grygorii.strashko@ti.com \
--cc=jhs@mojatatu.com \
--cc=jwi@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ubraun@linux.ibm.com \
--cc=xiyou.wangcong@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;
as well as URLs for NNTP newsgroup(s).