From: Guangbin Huang <huangguangbin2@huawei.com>
To: <davem@davemloft.net>, <kuba@kernel.org>, <xie.he.0141@gmail.com>,
<ms@dev.tdt.de>, <willemb@google.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<lipeng321@huawei.com>, <huangguangbin2@huawei.com>
Subject: [PATCH net-next 3/8] net: ixp4xx_hss: fix the code style issue about "foo* bar"
Date: Thu, 10 Jun 2021 15:20:00 +0800 [thread overview]
Message-ID: <1623309605-15671-4-git-send-email-huangguangbin2@huawei.com> (raw)
In-Reply-To: <1623309605-15671-1-git-send-email-huangguangbin2@huawei.com>
From: Peng Li <lipeng321@huawei.com>
Fix the checkpatch error as "foo* bar" and should be "foo *bar",
and "(foo*)" should be "(foo *)".
Signed-off-by: Peng Li <lipeng321@huawei.com>
Signed-off-by: Guangbin Huang <huangguangbin2@huawei.com>
---
drivers/net/wan/ixp4xx_hss.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/net/wan/ixp4xx_hss.c b/drivers/net/wan/ixp4xx_hss.c
index 6aa01d5..48bc914 100644
--- a/drivers/net/wan/ixp4xx_hss.c
+++ b/drivers/net/wan/ixp4xx_hss.c
@@ -332,7 +332,7 @@ static const struct {
* utility functions
****************************************************************************/
-static inline struct port* dev_to_port(struct net_device *dev)
+static inline struct port *dev_to_port(struct net_device *dev)
{
return dev_to_hdlc(dev)->priv;
}
@@ -351,9 +351,9 @@ static inline void memcpy_swab32(u32 *dest, u32 *src, int cnt)
* HSS access
****************************************************************************/
-static void hss_npe_send(struct port *port, struct msg *msg, const char* what)
+static void hss_npe_send(struct port *port, struct msg *msg, const char *what)
{
- u32 *val = (u32*)msg;
+ u32 *val = (u32 *)msg;
if (npe_send_message(port->npe, msg, what)) {
pr_crit("HSS-%i: unable to send command [%08X:%08X] to %s\n",
--
2.8.1
next prev parent reply other threads:[~2021-06-10 7:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 7:19 [PATCH net-next 0/8] net: ixp4xx_hss: clean up some code style issues Guangbin Huang
2021-06-10 7:19 ` [PATCH net-next 1/8] net: ixp4xx_hss: remove redundant blank lines Guangbin Huang
2021-06-10 7:19 ` [PATCH net-next 2/8] net: ixp4xx_hss: add blank line after declarations Guangbin Huang
2021-06-10 7:20 ` Guangbin Huang [this message]
2021-06-10 7:20 ` [PATCH net-next 4/8] net: ixp4xx_hss: move out assignment in if condition Guangbin Huang
2021-06-10 7:20 ` [PATCH net-next 5/8] net: ixp4xx_hss: add some required spaces Guangbin Huang
2021-06-10 7:20 ` [PATCH net-next 6/8] net: ixp4xx_hss: remove redundant spaces Guangbin Huang
2021-06-10 7:20 ` [PATCH net-next 7/8] net: ixp4xx_hss: fix the comments style issue Guangbin Huang
2021-06-10 7:20 ` [PATCH net-next 8/8] net: ixp4xx_hss: add braces {} to all arms of the statement Guangbin Huang
2021-06-10 21:00 ` [PATCH net-next 0/8] net: ixp4xx_hss: clean up some code style issues patchwork-bot+netdevbpf
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=1623309605-15671-4-git-send-email-huangguangbin2@huawei.com \
--to=huangguangbin2@huawei.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lipeng321@huawei.com \
--cc=ms@dev.tdt.de \
--cc=netdev@vger.kernel.org \
--cc=willemb@google.com \
--cc=xie.he.0141@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).