From: Weihang Li <liweihang@huawei.com>
To: <davem@davemloft.net>, <kuba@kernel.org>, <andrew@lunn.ch>,
<hkallweit1@gmail.com>
Cc: <netdev@vger.kernel.org>, <linuxarm@huawei.com>,
Weihang Li <liweihang@huawei.com>
Subject: [PATCH net-next 0/8] net: phy: fix some coding-style issues
Date: Fri, 11 Jun 2021 14:36:51 +0800 [thread overview]
Message-ID: <1623393419-2521-1-git-send-email-liweihang@huawei.com> (raw)
Make some cleanups according to the coding style of kernel.
Wenpeng Liang (8):
net: phy: add a blank line after declarations
net: phy: correct format of block comments
net: phy: delete repeated word of block comments
net: phy: fixed formatting issues with braces
net: phy: fixed space alignment issues
net: phy: print the function name by __func__ instead of an fixed
string
net: phy: remove unnecessary line continuation
net: phy: use '__packed' instead of '__attribute__((__packed__))'
drivers/net/phy/bcm87xx.c | 4 +-
drivers/net/phy/davicom.c | 4 +-
drivers/net/phy/dp83640.c | 5 +-
drivers/net/phy/et1011c.c | 12 +--
drivers/net/phy/fixed_phy.c | 4 +-
drivers/net/phy/lxt.c | 6 +-
drivers/net/phy/marvell.c | 9 +--
drivers/net/phy/mdio_bus.c | 1 +
drivers/net/phy/mdio_device.c | 4 +-
drivers/net/phy/mscc/mscc_ptp.h | 4 +-
drivers/net/phy/national.c | 6 +-
drivers/net/phy/phy-c45.c | 2 +-
drivers/net/phy/phy-core.c | 161 ++++++++++++++++++++--------------------
drivers/net/phy/phy.c | 3 +-
drivers/net/phy/phy_device.c | 9 +--
drivers/net/phy/phylink.c | 14 ++--
drivers/net/phy/qsemi.c | 1 +
drivers/net/phy/sfp-bus.c | 28 +++----
drivers/net/phy/sfp.c | 2 +-
drivers/net/phy/spi_ks8995.c | 10 +--
drivers/net/phy/ste10Xp.c | 6 +-
drivers/net/phy/vitesse.c | 3 +-
22 files changed, 153 insertions(+), 145 deletions(-)
--
2.8.1
next reply other threads:[~2021-06-11 6:40 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 6:36 Weihang Li [this message]
2021-06-11 6:36 ` [PATCH net-next 1/8] net: phy: add a blank line after declarations Weihang Li
2021-06-11 14:31 ` Andrew Lunn
2021-06-15 6:12 ` liweihang
2021-06-11 6:36 ` [PATCH net-next 2/8] net: phy: correct format of block comments Weihang Li
2021-06-11 14:36 ` Andrew Lunn
2021-06-15 6:18 ` liweihang
2021-06-11 6:36 ` [PATCH net-next 3/8] net: phy: delete repeated word " Weihang Li
2021-06-11 14:39 ` Andrew Lunn
2021-06-15 6:21 ` liweihang
2021-06-11 6:36 ` [PATCH net-next 4/8] net: phy: fixed formatting issues with braces Weihang Li
2021-06-11 14:41 ` Andrew Lunn
2021-06-16 6:39 ` liweihang
2021-06-11 6:36 ` [PATCH net-next 5/8] net: phy: fixed space alignment issues Weihang Li
2021-06-11 15:30 ` Andrew Lunn
2021-06-15 6:24 ` liweihang
2021-06-11 6:36 ` [PATCH net-next 6/8] net: phy: print the function name by __func__ instead of an fixed string Weihang Li
2021-06-11 16:05 ` Andrew Lunn
2021-06-15 6:26 ` liweihang
2021-06-16 8:14 ` liweihang
2021-06-11 6:36 ` [PATCH net-next 7/8] net: phy: remove unnecessary line continuation Weihang Li
2021-06-11 16:06 ` Andrew Lunn
2021-06-15 6:26 ` liweihang
2021-06-11 6:36 ` [PATCH net-next 8/8] net: phy: use '__packed' instead of '__attribute__((__packed__))' Weihang Li
2021-06-11 16:07 ` Andrew Lunn
2021-06-14 14:28 ` David Laight
2021-06-16 6:17 ` liweihang
2021-06-16 8:47 ` David Laight
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=1623393419-2521-1-git-send-email-liweihang@huawei.com \
--to=liweihang@huawei.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linuxarm@huawei.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.