[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b4ab8f64-7b33-4365-9ad5-510171a7f9b8@gmail.com>
Date: Wed, 13 Mar 2024 13:39:35 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Andrew Lunn <andrew@...n.ch>
Cc: Ronnie.Kunin@...rochip.com, Raju.Lakkaraju@...rochip.com,
netdev@...r.kernel.org, davem@...emloft.net, kuba@...nel.org,
linux-kernel@...r.kernel.org, Bryan.Whitehead@...rochip.com,
richardcochran@...il.com, UNGLinuxDriver@...rochip.com
Subject: Re: [PATCH net 3/3] net: lan743x: Address problems with wake option
flags configuration sequences
On 3/13/24 12:52, Andrew Lunn wrote:
> So i think we need to agree on best practices for new drivers and
> document what that is, probably in both the ethtool man page and
> include/uapi/linux/ethtool.h
>
> * WAKE_MAGIC on its own is O.K.
> * WAKE_MAGICSECURE without WAKE_MAGIC is invalid. -EINVAL
> * WAKE_MAGIC + WAKE_MAGICSECURE means only secure magic WoL.
> * Each driver needs to enforce this, due to backwards compatibility.
> Some may decide not to.
>
> Can we agree on this?
Yes, that works for me as well.
--
Florian
Powered by blists - more mailing lists