From: Vladimir Oltean <olteanv@gmail.com>
To: Jerry Ray <jerry.ray@microchip.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@armlinux.org.uk
Subject: Re: [PATCH net-next v4 1/2] dsa: lan9303: Whitespace Only
Date: Thu, 8 Dec 2022 19:11:12 +0200 [thread overview]
Message-ID: <20221208171112.eimyx4szcug5wr6u@skbuf> (raw)
In-Reply-To: <20221207232828.7367-2-jerry.ray@microchip.com>
Please name the commit message something more specific than "Whitespace Only",
that is likely to not be confused with some other patch. A "Whitespace Only"
patch can take place anywhere in this file. Like "align dsa_switch_ops members".
On Wed, Dec 07, 2022 at 05:28:27PM -0600, Jerry Ray wrote:
> Whitespace preparatory patch, making the dsa_switch_ops table consistent.
> No code is added or removed.
>
> Signed-off-by: Jerry Ray <jerry.ray@microchip.com>
> ---
> drivers/net/dsa/lan9303-core.c | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/net/dsa/lan9303-core.c b/drivers/net/dsa/lan9303-core.c
> index 80f07bd20593..d9f7b554a423 100644
> --- a/drivers/net/dsa/lan9303-core.c
> +++ b/drivers/net/dsa/lan9303-core.c
> @@ -1280,16 +1280,16 @@ static int lan9303_port_mdb_del(struct dsa_switch *ds, int port,
> }
>
> static const struct dsa_switch_ops lan9303_switch_ops = {
> - .get_tag_protocol = lan9303_get_tag_protocol,
> - .setup = lan9303_setup,
> - .get_strings = lan9303_get_strings,
> - .phy_read = lan9303_phy_read,
> - .phy_write = lan9303_phy_write,
> - .adjust_link = lan9303_adjust_link,
> - .get_ethtool_stats = lan9303_get_ethtool_stats,
> - .get_sset_count = lan9303_get_sset_count,
> - .port_enable = lan9303_port_enable,
> - .port_disable = lan9303_port_disable,
> + .get_tag_protocol = lan9303_get_tag_protocol,
> + .setup = lan9303_setup,
> + .get_strings = lan9303_get_strings,
> + .phy_read = lan9303_phy_read,
> + .phy_write = lan9303_phy_write,
> + .adjust_link = lan9303_adjust_link,
> + .get_ethtool_stats = lan9303_get_ethtool_stats,
> + .get_sset_count = lan9303_get_sset_count,
> + .port_enable = lan9303_port_enable,
> + .port_disable = lan9303_port_disable,
Do you use a text editor which highlights tabs? The members above this
line are aligned with tabs, the ones below with spaces. Still not
exactly what I'd call "consistent".
> .port_bridge_join = lan9303_port_bridge_join,
> .port_bridge_leave = lan9303_port_bridge_leave,
> .port_stp_state_set = lan9303_port_stp_state_set,
> --
> 2.17.1
>
next prev parent reply other threads:[~2022-12-08 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 23:28 [PATCH net-next v4 0/2] dsa: lan9303: Move to PHYLINK Jerry Ray
2022-12-07 23:28 ` [PATCH net-next v4 1/2] dsa: lan9303: Whitespace Only Jerry Ray
2022-12-08 17:11 ` Vladimir Oltean [this message]
2022-12-09 19:25 ` Jerry.Ray
2022-12-09 22:13 ` Vladimir Oltean
2022-12-07 23:28 ` [PATCH net-next v4 2/2] dsa: lan9303: Migrate to PHYLINK Jerry Ray
2022-12-08 17:21 ` Vladimir Oltean
2022-12-09 18:00 ` Jerry.Ray
2022-12-09 18:07 ` Vladimir Oltean
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=20221208171112.eimyx4szcug5wr6u@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=jerry.ray@microchip.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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