From: hanyu001@208suo.com
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] 3c59x: Add space around '='
Date: Mon, 17 Jul 2023 11:27:10 +0800 [thread overview]
Message-ID: <304ca645a55aa0affe830bd36edaf24d@208suo.com> (raw)
In-Reply-To: <tencent_7B6F5BD00E87F90524CC452645A9D0DB2007@qq.com>
Fix checkpatch warnings:
./drivers/net/ethernet/3com/3c59x.c:716: ERROR: spaces required around
that '=' (ctx:VxV)
./drivers/net/ethernet/3com/3c59x.c:717: ERROR: spaces required around
that '=' (ctx:VxV)
./drivers/net/ethernet/3com/3c59x.c:717: ERROR: spaces required around
that '=' (ctx:VxV)
./drivers/net/ethernet/3com/3c59x.c:717: ERROR: spaces required around
that '=' (ctx:VxV)
./drivers/net/ethernet/3com/3c59x.c:717: ERROR: spaces required around
that '=' (ctx:VxV)
Signed-off-by: maqimei <2433033762@qq.com>
---
drivers/net/ethernet/3com/3c59x.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/3com/3c59x.c
b/drivers/net/ethernet/3com/3c59x.c
index 082388b..9aa3244 100644
--- a/drivers/net/ethernet/3com/3c59x.c
+++ b/drivers/net/ethernet/3com/3c59x.c
@@ -713,8 +713,8 @@ static void window_set(struct vortex_private *vp,
int window)
Note that we deviate from the 3Com order by checking 10base2 before
AUI.
*/
enum xcvr_types {
- XCVR_10baseT=0, XCVR_AUI, XCVR_10baseTOnly, XCVR_10base2,
XCVR_100baseTx,
- XCVR_100baseFx, XCVR_MII=6, XCVR_NWAY=8, XCVR_ExtMII=9,
XCVR_Default=10,
+ XCVR_10baseT = 0, XCVR_AUI, XCVR_10baseTOnly, XCVR_10base2,
XCVR_100baseTx,
+ XCVR_100baseFx, XCVR_MII = 6, XCVR_NWAY = 8, XCVR_ExtMII = 9,
XCVR_Default = 10,
};
static const struct media_table {
next parent reply other threads:[~2023-07-17 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tencent_7B6F5BD00E87F90524CC452645A9D0DB2007@qq.com>
2023-07-17 3:27 ` hanyu001 [this message]
2023-07-18 17:42 ` [PATCH] 3c59x: Add space around '=' Jakub Kicinski
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=304ca645a55aa0affe830bd36edaf24d@208suo.com \
--to=hanyu001@208suo.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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