Re: [PATCH net-next v3 1/2] net: dsa: mv88e6xxx: Add functionality for handling RMU frames.

[Andrew Lunn <andrew@lunn.ch>]

On Mon, Sep 05, 2022 at 03:19:16PM +0200, Mattias Forsblad wrote:
> The Marvell SOHO family has a secondary channel for sending
> control data other than the ordinary MDIO channel. The
> switch can process specially crafted ethernet frames
> as control frames. Add functionality for creating, sending,
> receiving and processing those frames. This channel is
> best suited for accessing larger data structures in the
> switch.
> Use this control channel for getting RMON counters.
> 
> Signed-off-by: Mattias Forsblad <mattias.forsblad@gmail.com>
> ---
>  drivers/net/dsa/mv88e6xxx/Makefile  |   1 +
>  drivers/net/dsa/mv88e6xxx/chip.c    |  73 +++++--
>  drivers/net/dsa/mv88e6xxx/chip.h    |  21 ++
>  drivers/net/dsa/mv88e6xxx/global1.c |  76 +++++++
>  drivers/net/dsa/mv88e6xxx/global1.h |   3 +
>  drivers/net/dsa/mv88e6xxx/rmu.c     | 310 ++++++++++++++++++++++++++++
>  drivers/net/dsa/mv88e6xxx/rmu.h     |  28 +++
>  include/net/dsa.h                   |  20 +-
>  net/dsa/dsa.c                       |  28 +++
>  net/dsa/dsa2.c                      |   2 +
>  net/dsa/tag_dsa.c                   |  32 ++-

Please try to break this up into lots of small patches, each patch
doing one thing. It is O.K, to add a helper in one patch, and then a
user of that helper in a later patch, for example. You can add the
common code in dsa.c and then in a later patch make use of it. You can
add the rmu_enable code in one patch, and then use it later, etc.

Ideally, you want lots of small patches, each with a good commit
message, all of which are obviously correct.

I've not looked at the details yet of this patch. I will try to do so
later. My main aim at the moment is to get your changes into the right
sort of structure and the right sort of shape.

     Andrew