[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250829165846.1cee2798@kernel.org>
Date: Fri, 29 Aug 2025 16:58:46 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Kory Maincent <kory.maincent@...tlin.com>
Cc: Oleksij Rempel <o.rempel@...gutronix.de>, Andrew Lunn
<andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>, Eric
Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
kernel@...gutronix.de, Dent Project <dentproject@...uxfoundation.org>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, Maxime Chevallier
<maxime.chevallier@...tlin.com>
Subject: Re: [PATCH net-next 1/2] net: pse-pd: pd692x0: Separate
configuration parsing from hardware setup
On Fri, 29 Aug 2025 10:26:24 +0200 Kory Maincent wrote:
> > > I don't think so, as manager is declared like the following it should not.
> > > struct pd692x0_manager *manager __free(kfree) = NULL;
> >
> > Please consult documentation on the user of __free() within networking.
>
> Oh, I didn't know about this net policy.
> I didn't follow the maintainer-netdev doc changes. Maybe I should.
> Ok, I will add a patch to the series to remove the __free macro.
Up to you on existing code, but maybe avoid using it in the future?
Powered by blists - more mailing lists