From: Vladimir Oltean <olteanv@gmail.com>
To: Arseny Solokha <asolokha@kb.kras.ru>
Cc: Claudiu Manoil <claudiu.manoil@nxp.com>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Russell King <linux@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 0/4] gianfar: some assorted cleanup
Date: Thu, 5 Sep 2019 13:39:41 +0300 [thread overview]
Message-ID: <CA+h21hpbtsJtUSVUqRO1mpi+Y-KxEi-BfesbDF80bgH-QGAAnQ@mail.gmail.com> (raw)
In-Reply-To: <20190904135223.31754-1-asolokha@kb.kras.ru>
On Wed, 4 Sep 2019 at 16:53, Arseny Solokha <asolokha@kb.kras.ru> wrote:
>
> This is a cleanup series for the gianfar Ethernet driver, following up a
> discussion in [1]. It is intended to precede a conversion of gianfar from
> PHYLIB to PHYLINK API, which will be submitted later in its version 2.
> However, it won't make a conversion cleaner, except for the last patch in
> this series. Obviously this series is not intended for -stable.
>
> The first patch looks super controversial to me, as it moves lots of code
> around for the sole purpose of getting rid of static forward declarations
> in two translation units. On the other hand, this change is purely
> mechanical and cannot do any harm other than cluttering git blame output.
> I can prepare an alternative patch for only swapping adjacent functions
> around, if necessary.
>
> The second patch is a trivial follow-up to the first one, making functions
> that are only called from the same translation unit static.
>
> The third patch removes some now unused macro and structure definitions
> from gianfar.h, slipped away from various cleanups in the past.
>
> The fourth patch, also suggested in [1], makes the driver consistently use
> PHY connection type value obtained from a Device Tree node, instead of
> ignoring it and using the one auto-detected by MAC, when connecting to PHY.
> Obviously a value has to be specified correctly in DT source, or omitted
> altogether, in which case the driver will fall back to auto-detection. When
> querying a DT node, the driver will also take both applicable properties
> into account by making a proper API call instead of open-coding the lookup
> half-way correctly.
>
> [1] https://lore.kernel.org/netdev/CA+h21hruqt6nGG5ksDSwrGH_w5GtGF4fjAMCWJne7QJrjusERQ@mail.gmail.com/
>
> Arseny Solokha (4):
> gianfar: remove forward declarations
> gianfar: make five functions static
> gianfar: cleanup gianfar.h
> gianfar: use DT more consistently when selecting PHY connection type
>
> drivers/net/ethernet/freescale/gianfar.c | 4647 ++++++++---------
> drivers/net/ethernet/freescale/gianfar.h | 45 -
> .../net/ethernet/freescale/gianfar_ethtool.c | 13 -
> 3 files changed, 2303 insertions(+), 2402 deletions(-)
>
> --
> 2.23.0
>
Thanks for the cleanup!
-Vladimir
next prev parent reply other threads:[~2019-09-05 10:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-23 15:17 [RFC PATCH 0/2] convert gianfar to phylink Arseny Solokha
2019-07-23 15:17 ` [RFC PATCH 1/2] gianfar: convert " Arseny Solokha
2019-07-23 16:07 ` Claudiu Manoil
2019-07-24 7:36 ` Arseny Solokha
2019-07-24 8:19 ` Russell King - ARM Linux admin
2019-07-29 23:39 ` Vladimir Oltean
2019-07-30 10:23 ` Russell King - ARM Linux admin
2019-08-24 12:49 ` Vladimir Oltean
2019-07-30 14:40 ` Arseny Solokha
2019-08-24 15:21 ` Vladimir Oltean
2019-08-28 15:20 ` Vladimir Oltean
2019-09-04 13:52 ` [PATCH 0/4] gianfar: some assorted cleanup Arseny Solokha
2019-09-04 13:52 ` [PATCH 1/4] gianfar: remove forward declarations Arseny Solokha
2019-09-04 13:52 ` [PATCH 2/4] gianfar: make five functions static Arseny Solokha
2019-09-04 13:52 ` [PATCH 3/4] gianfar: cleanup gianfar.h Arseny Solokha
2019-09-04 13:52 ` [PATCH 4/4] gianfar: use DT more consistently when selecting PHY connection type Arseny Solokha
2019-09-05 10:28 ` [PATCH 0/4] gianfar: some assorted cleanup David Miller
2019-09-05 10:39 ` Vladimir Oltean [this message]
2019-09-04 13:54 ` [RFC PATCH 1/2] gianfar: convert to phylink Arseny Solokha
2019-09-04 13:53 ` Arseny Solokha
2019-07-23 15:17 ` [RFC PATCH 2/2] net: phylink: don't start and stop SGMII PHYs in SFP modules twice Arseny Solokha
2019-07-24 9:01 ` Russell King - ARM Linux admin
2019-07-24 13:31 ` [PATCH v2] " Arseny Solokha
2019-07-24 13:36 ` Andrew Lunn
2019-07-24 13:37 ` Russell King - ARM Linux admin
2019-07-24 21:38 ` David Miller
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=CA+h21hpbtsJtUSVUqRO1mpi+Y-KxEi-BfesbDF80bgH-QGAAnQ@mail.gmail.com \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=asolokha@kb.kras.ru \
--cc=claudiu.manoil@nxp.com \
--cc=f.fainelli@gmail.com \
--cc=ioana.ciornei@nxp.com \
--cc=linux@armlinux.org.uk \
--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 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).