linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Donald Hunter <donald.hunter@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	Dent Project <dentproject@linuxfoundation.org>,
	kernel@pengutronix.de, linux-doc@vger.kernel.org
Subject: Re: [PATCH net-next v5 5/7] net: ethtool: Add new power limit get and set features
Date: Fri, 28 Jun 2024 11:00:30 +0200	[thread overview]
Message-ID: <Zn57rqFgDq7rg1pA@pengutronix.de> (raw)
In-Reply-To: <20240628-feature_poe_power_cap-v5-5-5e1375d3817a@bootlin.com>

On Fri, Jun 28, 2024 at 10:31:58AM +0200, Kory Maincent wrote:
> From: Kory Maincent (Dent Project) <kory.maincent@bootlin.com>
> 
> This patch expands the status information provided by ethtool for PSE c33
> with available power limit and available power limit ranges. It also adds
> a call to pse_ethtool_set_pw_limit() to configure the PSE control power
> limit.
> 
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>

Reviewed-by: Oleksij Rempel <o.rempel@pengutronix.de>

Thank you!
-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2024-06-28  9:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-28  8:31 [PATCH net-next v5 0/7] net: pse-pd: Add new PSE c33 features Kory Maincent
2024-06-28  8:31 ` [PATCH net-next v5 1/7] net: ethtool: pse-pd: Expand C33 PSE status with class, power and extended state Kory Maincent
2024-06-28  8:31 ` [PATCH net-next v5 2/7] netlink: specs: Expand the PSE netlink command with C33 new features Kory Maincent
2024-07-02 13:19   ` Paolo Abeni
2024-06-28  8:31 ` [PATCH net-next v5 3/7] net: pse-pd: pd692x0: Expand ethtool status message Kory Maincent
2024-06-28  8:36   ` Oleksij Rempel
2024-06-28  8:31 ` [PATCH net-next v5 4/7] net: pse-pd: Add new power limit get and set c33 features Kory Maincent
2024-06-28  8:53   ` Oleksij Rempel
2024-06-28  8:31 ` [PATCH net-next v5 5/7] net: ethtool: Add new power limit get and set features Kory Maincent
2024-06-28  9:00   ` Oleksij Rempel [this message]
2024-06-28  8:31 ` [PATCH net-next v5 6/7] netlink: specs: Expand the PSE netlink command with C33 pw-limit attributes Kory Maincent
2024-06-28  8:32 ` [PATCH net-next v5 7/7] net: pse-pd: pd692x0: Enhance with new current limit and voltage read callbacks Kory Maincent
2024-06-28  9:06   ` 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=Zn57rqFgDq7rg1pA@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=dentproject@linuxfoundation.org \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=kernel@pengutronix.de \
    --cc=kory.maincent@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=thomas.petazzoni@bootlin.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;
as well as URLs for NNTP newsgroup(s).