From: Mohammed Anees <pvmohammedanees2003@gmail.com>
To: andrew@lunn.ch
Cc: davem@davemloft.net, edumazet@google.com, f.fainelli@gmail.com,
kuba@kernel.org, linux-kernel@vger.kernel.org,
linux@armlinux.org.uk, netdev@vger.kernel.org, olteanv@gmail.com,
pabeni@redhat.com, pvmohammedanees2003@gmail.com
Subject: Re: [PATCH] net: dsa: Fix conditional handling of Wake-on-Lan configuration in dsa_user_set_wol
Date: Sun, 6 Oct 2024 00:12:33 +0530 [thread overview]
Message-ID: <20241005184235.22421-1-pvmohammedanees2003@gmail.com> (raw)
In-Reply-To: <8555d3b6-8154-4a79-9828-352641ca0a58@lunn.ch>
In the original code, we initialize ret = -EOPNOTSUPP and then call
phylink_ethtool_set_wol(). If DSA supports WOL, we call set_wol().
However, we aren’t checking if phylink_ethtool_set_wol() succeeds,
so I assumed both functions should be called, and if either fails,
we return -EOPNOTSUPP.
static int dsa_user_set_wol(struct net_device *dev, struct ethtool_wolinfo *w)
{
struct dsa_port *dp = dsa_user_to_port(dev);
struct dsa_switch *ds = dp->ds;
int ret = -EOPNOTSUPP;
phylink_ethtool_set_wol(dp->pl, w);
if (ds->ops->set_wol)
ret = ds->ops->set_wol(ds, dp->index, w);
return ret;
}
From your response, it seems either of the two function can handle setting
WOL, if so shouldn't we check the return value of phylink_ethtool_set_wol()
to ensure it succeeds?
Thanks!
next prev parent reply other threads:[~2024-10-05 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 22:02 [PATCH] net: dsa: Fix conditional handling of Wake-on-Lan configuration in dsa_user_set_wol Mohammed Anees
2024-10-05 16:49 ` Andrew Lunn
2024-10-05 18:42 ` Mohammed Anees [this message]
2024-10-05 21:00 ` Andrew Lunn
2024-10-06 16:10 ` Mohammed Anees
2024-10-06 19:57 ` Andrew Lunn
2024-10-06 22:41 ` Mohammed Anees
2024-10-07 8:56 ` Russell King (Oracle)
2024-10-07 22:22 ` Mohammed Anees
-- strict thread matches above, loose matches on Subject: below --
2024-10-07 22:22 [PATCH v2] " Vladimir Oltean
2024-10-07 22:43 ` [PATCH] " Mohammed Anees
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=20241005184235.22421-1-pvmohammedanees2003@gmail.com \
--to=pvmohammedanees2003@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--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