Netdev List
 help / color / mirror / Atom feed
From: "Markus Stockhausen" <markus.stockhausen@gmx.de>
To: "'Jakub Kicinski'" <kuba@kernel.org>
Cc: <andrew@lunn.ch>, <hkallweit1@gmail.com>, <linux@armlinux.org.uk>,
	<davem@davemloft.net>, <edumazet@google.com>, <pabeni@redhat.com>,
	<netdev@vger.kernel.org>, <chris.packham@alliedtelesis.co.nz>,
	<daniel@makrotopia.org>, <mensi@mensi.ch>
Subject: AW: [PATCH net-next 1/8] net: mdio: realtek-rtl9300: Convert to fwnode API
Date: Tue, 2 Jun 2026 20:58:38 +0200	[thread overview]
Message-ID: <00b701dcf2c1$d38215c0$7a864140$@gmx.de> (raw)
In-Reply-To: <20260602110535.13ed4664@kernel.org>

> Von: Jakub Kicinski <kuba@kernel.org> 
> Gesendet: Dienstag, 2. Juni 2026 20:06
> An: Markus Stockhausen <markus.stockhausen@gmx.de>
> Betreff: Re: [PATCH net-next 1/8] net: mdio: realtek-rtl9300: Convert to
fwnode API
> 
> On Tue,  2 Jun 2026 07:26:33 +0200 Markus Stockhausen wrote:
> > -		struct device_node *phy_dn __free(device_node) =
> > -			of_parse_phandle(to_of_node(port), "phy-handle", 0);
> > +		struct fwnode_handle *phy_fwnode __free(fwnode_handle) =
> > +			fwnode_find_reference(port, "phy-handle", 0);
> >  		/* skip ports without phys */
> > -		if (!phy_dn)
> > +		if (IS_ERR(phy_fwnode))
> >  			continue;
> >  
> > -		mdio_dn = phy_dn->parent;
> > +		struct fwnode_handle *bus_fwnode __free(fwnode_handle) =
> > +			fwnode_get_parent(phy_fwnode);
> > +		if (!bus_fwnode)
> > +			continue;
>
> Variable declarations mid functions are a no-go for netdev.
>
> If you could please move away from using the __free() crap I'd
> appreciate. Clearly missed it yesterday when applying these patches

Thanks for the reminder.

Yesterdays patches should contain neither of those. For the
new series I stupidly assumed that the existing __free usage
is accepted. Will take care about this for v2 and future patches.

Markus


  reply	other threads:[~2026-06-02 18:58 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02  5:26 [PATCH net-next 0/8] net: mdio: realtek-rtl9300: Refactor initialization and port lookup Markus Stockhausen
2026-06-02  5:26 ` [PATCH net-next 1/8] net: mdio: realtek-rtl9300: Convert to fwnode API Markus Stockhausen
2026-06-02 12:06   ` Andrew Lunn
2026-06-02 12:29     ` AW: " Markus Stockhausen
2026-06-02 12:50       ` Andrew Lunn
2026-06-02 18:05   ` Jakub Kicinski
2026-06-02 18:58     ` Markus Stockhausen [this message]
2026-06-02  5:26 ` [PATCH net-next 2/8] net: mdio: realtek-rtl9300: Correctly handle ethernet-phy-package Markus Stockhausen
2026-06-02  9:32   ` Jagielski, Jedrzej
2026-06-02 10:23     ` AW: " Markus Stockhausen
2026-06-02 11:22       ` Jagielski, Jedrzej
2026-06-02  5:26 ` [PATCH net-next 3/8] net: mdio: realtek-rtl9300: harden otto_emdio_map_ports() Markus Stockhausen
2026-06-02  9:38   ` Jagielski, Jedrzej
2026-06-02 10:42     ` AW: " Markus Stockhausen
2026-06-02 11:29       ` Jagielski, Jedrzej
2026-06-02 12:14   ` Andrew Lunn
2026-06-02  5:26 ` [PATCH net-next 4/8] net: mdio: realtek-rtl9300: harden otto_emdio_probe_one() Markus Stockhausen
2026-06-02  5:26 ` [PATCH net-next 5/8] net: mdio: realtek-rtl9300: adapt spaces for defines Markus Stockhausen
2026-06-02  9:42   ` Jagielski, Jedrzej
2026-06-02 10:18     ` AW: " Markus Stockhausen
2026-06-02 11:16       ` Jagielski, Jedrzej
2026-06-02 12:20   ` Andrew Lunn
2026-06-02  5:26 ` [PATCH net-next 6/8] net: mdio: realtek-rtl9300: relocate topology setup Markus Stockhausen
2026-06-02  9:50   ` Jagielski, Jedrzej
2026-06-02 10:50     ` AW: " Markus Stockhausen
2026-06-02 12:24   ` Andrew Lunn
2026-06-02 13:01     ` AW: " Markus Stockhausen
2026-06-02 15:17       ` Andrew Lunn
2026-06-02 18:48         ` AW: " Markus Stockhausen
2026-06-02 20:29           ` Andrew Lunn
2026-06-02  5:26 ` [PATCH net-next 7/8] net: mdio: realtek-rtl9300: reorder controller setup Markus Stockhausen
2026-06-02  5:26 ` [PATCH net-next 8/8] net: mdio: realtek-rtl9300: Convert port lookup from O(n) to O(1) Markus Stockhausen
2026-06-02 12:30   ` Andrew Lunn
2026-06-02 20:02     ` AW: " Markus Stockhausen

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='00b701dcf2c1$d38215c0$7a864140$@gmx.de' \
    --to=markus.stockhausen@gmx.de \
    --cc=andrew@lunn.ch \
    --cc=chris.packham@alliedtelesis.co.nz \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=mensi@mensi.ch \
    --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