[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6317ad1e-7507-4a61-92d0-865c52736b1a@lunn.ch>
Date: Mon, 25 Aug 2025 14:18:25 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Oleksij Rempel <o.rempel@...gutronix.de>
Cc: Kory Maincent <kory.maincent@...tlin.com>,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, 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>,
Kyle Swenson <kyle.swenson@....tech>
Subject: Re: [PATCH net-next 2/2] net: pse-pd: pd692x0: Add sysfs interface
for configuration save/reset
On Mon, Aug 25, 2025 at 11:14:03AM +0200, Oleksij Rempel wrote:
> Hello Kory,
>
> On Mon, Aug 25, 2025 at 10:47:21AM +0200, Kory Maincent wrote:
> > > I've not looked at the sysfs documentation. Are there other examples
> > > of such a property?
> >
> > Not sure for that particular save/reset configuration case.
> > Have you another implementation idea in mind?
>
> My personal preference would be to use devlink (netlink based)
> interface.
Yes, devlink also crossed my mind, probably devlink params. Although
saving the current configuration to non-volatile memory is more a meta
parameter.
Andrew
Powered by blists - more mailing lists