public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Oltean <olteanv@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: 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>,
	Russell King <linux@armlinux.org.uk>,
	Gregory Clement <gregory.clement@bootlin.com>,
	netdev@vger.kernel.org, Vladimir Oltean <vladimir.oltean@nxp.com>
Subject: Re: [PATCH net-next v4 3/8] net: dsa: move call to driver port_setup after creation of netdev
Date: Thu, 11 Apr 2024 02:50:52 +0300	[thread overview]
Message-ID: <20240410235052.utn6c2ryyfxgo4zq@skbuf> (raw)
In-Reply-To: <20240406-v6-8-0-net-next-mv88e6xxx-leds-v4-v4-3-eb97665e7f96@lunn.ch>

On Sat, Apr 06, 2024 at 03:13:30PM -0500, Andrew Lunn wrote:
> From: Vladimir Oltean <vladimir.oltean@nxp.com>
> 
> The driver-facing method port_setup() is a good place to add the LEDs of
> a port to the netdev representing the port. However, when port_setup()
> is called in dsa_port_devlink_setup(), the netdev does not exist
> yet. That only happens in dsa_user_create(), which is later in
> dsa_port_setup().
> 
> Move the call to port_setup() out of dsa_port_devlink_setup() and to
> the end of dsa_port_setup() where the netdev will exist. For the other
> port types, the call to port_setup() and port_teardown() remains where
> it was before (functionally speaking), but now it needs to be open-coded
> in their respective setup/teardown logic.
> 
> Signed-off-by: Vladimir Oltean <vladimir.oltean@nxp.com>
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> ---

You can keep your author name and me as co-developer. If I changed your
author information it was probably a mistake.

  reply	other threads:[~2024-04-10 23:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-06 20:13 [PATCH net-next v4 0/8] net: Add generic support for netdev LEDs Andrew Lunn
2024-04-06 20:13 ` [PATCH net-next v4 1/8] net: dsa: consolidate setup and teardown for shared ports Andrew Lunn
2024-04-06 20:13 ` [PATCH net-next v4 2/8] net: dsa: break out port setup and teardown code per port type Andrew Lunn
2024-04-06 20:13 ` [PATCH net-next v4 3/8] net: dsa: move call to driver port_setup after creation of netdev Andrew Lunn
2024-04-10 23:50   ` Vladimir Oltean [this message]
2024-04-06 20:13 ` [PATCH net-next v4 4/8] net: Add helpers for netdev LEDs Andrew Lunn
2024-04-07 17:26   ` Andrew Lunn
2024-04-10 23:32   ` Vladimir Oltean
2024-04-06 20:13 ` [PATCH net-next v4 5/8] net: dsa: mv88e6xxx: Add helpers for 6352 LED blink and brightness Andrew Lunn
2024-04-06 20:13 ` [PATCH net-next v4 6/8] net: dsa: mv88e6xxx: Tie the low level LED functions to device ops Andrew Lunn
2024-04-06 20:13 ` [PATCH net-next v4 7/8] dsa: mv88e6xxx: Create port/netdev LEDs Andrew Lunn
2024-04-10 23:45   ` Vladimir Oltean
2024-04-06 20:13 ` [PATCH net-next v4 8/8] arm: boot: dts: mvebu: linksys-mamba: Add Ethernet LEDs Andrew Lunn
2024-06-26 12:16 ` [PATCH net-next v4 0/8] net: Add generic support for netdev LEDs 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=20240410235052.utn6c2ryyfxgo4zq@skbuf \
    --to=olteanv@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=gregory.clement@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vladimir.oltean@nxp.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