All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Cawston <ross@r-sc.ca>
To: github@szelinsky.de
Cc: o.rempel@pengutronix.de, kory.maincent@bootlin.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, piotr.kubik@adtran.com,
	saikrishnag@marvell.com, horms@kernel.org, kyle.swenson@est.tech,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ross Cawston <ross@r-sc.ca>
Subject: Re: [PATCH net 00/10] net: pse-pd: assorted lifetime and error-path fixes
Date: Sun, 18 Oct 2026 16:32:29 -0700	[thread overview]
Message-ID: <20261018233229.462-1-ross@r-sc.ca> (raw)
In-Reply-To: <20261018082314.48950-1-github@szelinsky.de>

Hi Carlo,

I sent a fix to pse_core.c for net today as well, for the budget of PIs
with software power control:

https://lore.kernel.org/netdev/20261018182005.1193-1-ross@r-sc.ca/

It changes _pse_pi_disable(), pse_disable_pi_pol(), pse_pi_disable()
and pse_set_config_isr(), none of which your series touches, so I don't
expect the two to get in each other's way. If they do, I'm happy to
rebase mine on top of yours.

Separately: I have a driver for the Realtek RTL8239, two of which a
MokerLink POE-10G07110GSM switch drives directly with no PSE MCU, and it
uses devm_pse_poll_helper() and the PSE LED triggers from your "poll
path and LED trigger support" series. Is a v6 of that planned once these
fixes are in? I can test it on that switch, and would post the RTL8239
driver on top of it.

Ross

  parent reply	other threads:[~2026-10-18 23:32 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18  8:23 [PATCH net 00/10] net: pse-pd: assorted lifetime and error-path fixes Carlo Szelinsky
2026-10-18  8:23 ` [PATCH net 01/10] net: pse-pd: size the notification kfifo after defaulting nr_lines Carlo Szelinsky
2026-10-19  9:22   ` Kory Maincent
2026-10-18  8:23 ` [PATCH net 02/10] net: pse-pd: fix module refcount leak in pse_control_get_internal() Carlo Szelinsky
2026-10-19  8:51   ` netdev-bot+sashiko
2026-10-19 19:56     ` Carlo Szelinsky
2026-10-19  9:31   ` Kory Maincent
2026-10-19 19:56     ` Carlo Szelinsky
2026-10-18  8:23 ` [PATCH net 03/10] net: pse-pd: do not keep a failed IRQ in pcdev->irq Carlo Szelinsky
2026-10-19  9:33   ` Kory Maincent
2026-10-18  8:23 ` [PATCH net 04/10] net: pse-pd: do not reach a freed PHY from the notification worker Carlo Szelinsky
2026-10-19  8:51   ` netdev-bot+sashiko
2026-10-19 19:56     ` Carlo Szelinsky
2026-10-18  8:23 ` [PATCH net 05/10] net: pse-pd: check the PI state under the lock when setting a power limit Carlo Szelinsky
2026-10-19  8:51   ` netdev-bot+sashiko
2026-10-19 12:30     ` Kory Maincent
2026-10-19 19:56       ` Carlo Szelinsky
2026-10-20  5:40       ` Oleksij Rempel
2026-10-20 10:19         ` Kory Maincent
2026-10-19 19:56     ` Carlo Szelinsky
2026-10-18  8:23 ` [PATCH net 06/10] net: pse-pd: do not tie a shared power domain to its creator's devres Carlo Szelinsky
2026-10-19  8:51   ` netdev-bot+sashiko
2026-10-19 19:56     ` Carlo Szelinsky
2026-10-18  8:23 ` [PATCH net 07/10] net: pse-pd: pd692x0: release the manager power budget through devres Carlo Szelinsky
2026-10-19 12:45   ` Kory Maincent
2026-10-18  8:23 ` [PATCH net 08/10] net: pse-pd: pd692x0: defer probe while a manager supply is unresolved Carlo Szelinsky
2026-10-19 12:47   ` Kory Maincent
2026-10-18  8:23 ` [PATCH net 09/10] net: pse-pd: si3474: fix use-after-free in ancillary client error path Carlo Szelinsky
2026-10-19 12:50   ` Kory Maincent
2026-10-19 19:56     ` Carlo Szelinsky
2026-10-18  8:23 ` [PATCH net 10/10] net: pse-pd: reject a power limit whose current does not fit an int Carlo Szelinsky
2026-10-19 12:53   ` Kory Maincent
2026-10-19 19:56     ` Carlo Szelinsky
2026-10-18 23:32 ` Ross Cawston [this message]
2026-10-19 19:56   ` [PATCH net 00/10] net: pse-pd: assorted lifetime and error-path fixes Carlo Szelinsky

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=20261018233229.462-1-ross@r-sc.ca \
    --to=ross@r-sc.ca \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=github@szelinsky.de \
    --cc=horms@kernel.org \
    --cc=kory.maincent@bootlin.com \
    --cc=kuba@kernel.org \
    --cc=kyle.swenson@est.tech \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=pabeni@redhat.com \
    --cc=piotr.kubik@adtran.com \
    --cc=saikrishnag@marvell.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.