From: Jakub Kicinski <kuba@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Woojung Huh <woojung.huh@microchip.com>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, Arun.Ramadoss@microchip.com
Subject: Re: [PATCH net-next v1 1/4] net: phy: add driver specific get/set_eee support
Date: Thu, 19 Jan 2023 19:53:25 -0800 [thread overview]
Message-ID: <20230119195325.50528972@kernel.org> (raw)
In-Reply-To: <20230119131821.3832456-2-o.rempel@pengutronix.de>
On Thu, 19 Jan 2023 14:18:18 +0100 Oleksij Rempel wrote:
> + /** @get_eee: Set the EEE configuration */
set
> + int (*set_eee)(struct phy_device *phydev, struct ethtool_eee *e);
next prev parent reply other threads:[~2023-01-20 4:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 13:18 [PATCH net-next v1 0/4] net: add EEE support for KSZ9477 switch series Oleksij Rempel
2023-01-19 13:18 ` [PATCH net-next v1 1/4] net: phy: add driver specific get/set_eee support Oleksij Rempel
2023-01-20 3:53 ` Jakub Kicinski [this message]
2023-01-19 13:18 ` [PATCH net-next v1 2/4] net: phy: micrel: add EEE configuration support for KSZ9477 variants of PHYs Oleksij Rempel
2023-01-19 14:08 ` Andrew Lunn
2023-01-20 5:50 ` Oleksij Rempel
2023-01-19 19:25 ` Florian Fainelli
2023-01-20 5:55 ` Oleksij Rempel
2023-01-20 17:58 ` Florian Fainelli
2023-01-21 6:34 ` Oleksij Rempel
2023-01-19 13:18 ` [PATCH net-next v1 3/4] net: phy: micrel: disable 1000Mbit EEE support if 1000Mbit is not supported Oleksij Rempel
2023-01-19 13:18 ` [PATCH net-next v1 4/4] net: dsa: microchip: enable EEE support Oleksij Rempel
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=20230119195325.50528972@kernel.org \
--to=kuba@kernel.org \
--cc=Arun.Ramadoss@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=vivien.didelot@gmail.com \
--cc=woojung.huh@microchip.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.