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 7/8] net: pc300too: add some required spaces
Date: Fri, 11 Jun 2021 11:36:21 +0800 [thread overview]
Message-ID: <1623382582-37854-8-git-send-email-huangguangbin2@huawei.com> (raw)
In-Reply-To: <1623382582-37854-1-git-send-email-huangguangbin2@huawei.com>
From: Peng Li <lipeng321@huawei.com>
Add spaces required before the open parenthesis '('.
Add spaces required after that close brace '}'.
Signed-off-by: Peng Li <lipeng321@huawei.com>
Signed-off-by: Guangbin Huang <huangguangbin2@huawei.com>
---
drivers/net/wan/pc300too.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/net/wan/pc300too.c b/drivers/net/wan/pc300too.c
index ecce999..885dcc5 100644
--- a/drivers/net/wan/pc300too.c
+++ b/drivers/net/wan/pc300too.c
@@ -68,7 +68,7 @@ typedef struct {
u32 cs_base[4]; /* 3C-48h : Chip Select Base Addrs */
u32 intr_ctrl_stat; /* 4Ch : Interrupt Control/Status */
u32 init_ctrl; /* 50h : EEPROM ctrl, Init Ctrl, etc */
-}plx9050;
+} plx9050;
typedef struct port_s {
struct napi_struct napi;
@@ -85,7 +85,7 @@ typedef struct port_s {
u16 txlast;
u8 rxs, txs, tmc; /* SCA registers */
u8 chan; /* physical port # - 0 or 1 */
-}port_t;
+} port_t;
typedef struct card_s {
int type; /* RSV, X21, etc. */
@@ -100,7 +100,7 @@ typedef struct card_s {
u8 irq; /* interrupt request level */
port_t ports[2];
-}card_t;
+} card_t;
#define get_port(card, port) ((port) < (card)->n_ports ? \
(&(card)->ports[port]) : (NULL))
@@ -117,7 +117,7 @@ static void pc300_set_iface(port_t *port)
sca_out(EXS_TES1, (port->chan ? MSCI1_OFFSET : MSCI0_OFFSET) + EXS,
port->card);
- switch(port->settings.clock_type) {
+ switch (port->settings.clock_type) {
case CLOCK_INT:
rxs |= CLK_BRG; /* BRG output */
txs |= CLK_PIN_OUT | CLK_TX_RXCLK; /* RX clock */
--
2.8.1
next prev parent reply other threads:[~2021-06-11 3:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 3:36 [PATCH net-next 0/8] net: pc300too: clean up some code style issues Guangbin Huang
2021-06-11 3:36 ` [PATCH net-next 1/8] net: pc300too: remove redundant blank lines Guangbin Huang
2021-06-11 3:36 ` [PATCH net-next 2/8] net: pc300too: add blank line after declarations Guangbin Huang
2021-06-11 3:36 ` [PATCH net-next 3/8] net: pc300too: fix the code style issue about "foo * bar" Guangbin Huang
2021-06-11 3:36 ` [PATCH net-next 4/8] net: pc300too: move out assignment in if condition Guangbin Huang
2021-06-11 3:36 ` [PATCH net-next 5/8] net: pc300too: remove redundant initialization for statics Guangbin Huang
2021-06-11 3:36 ` [PATCH net-next 6/8] net: pc300too: replace comparison to NULL with "!card->plxbase" Guangbin Huang
2021-06-11 3:36 ` Guangbin Huang [this message]
2021-06-11 3:36 ` [PATCH net-next 8/8] net: pc300too: fix the comments style issue Guangbin Huang
2021-06-11 20:00 ` [PATCH net-next 0/8] net: pc300too: 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=1623382582-37854-8-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).