Netdev List
 help / color / mirror / Atom feed
From: Kory Maincent <kory.maincent@bootlin.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	kernel@pengutronix.de,
	Dent Project <dentproject@linuxfoundation.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] Preserve PSE PD692x0 configuration across reboots
Date: Tue, 30 Sep 2025 16:58:17 +0200	[thread overview]
Message-ID: <20250930165817.2e3e756d@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <89ed50ab-07da-4514-b240-ed3d05400e91@redhat.com>

On Tue, 30 Sep 2025 16:40:51 +0200
Paolo Abeni <pabeni@redhat.com> wrote:

> On 9/30/25 11:12 AM, Kory Maincent wrote:
> > From: Kory Maincent (Dent Project) <kory.maincent@bootlin.com>
> > 
> > Previously, the driver would always reconfigure the PSE hardware on
> > probe, causing a port matrix reflash that resulted in temporary power
> > loss to all connected devices. This change maintains power continuity
> > by preserving existing configuration when the PSE has been previously
> > initialized.
> > 
> > Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> > ---
> > Kory Maincent (3):
> >       net: pse-pd: pd692x0: Replace __free macro with explicit kfree calls
> >       net: pse-pd: pd692x0: Separate configuration parsing from hardware
> > setup net: pse-pd: pd692x0: Preserve PSE configuration across reboots
> > 
> >  drivers/net/pse-pd/pd692x0.c | 155
> > +++++++++++++++++++++++++++++++------------ 1 file changed, 112
> > insertions(+), 43 deletions(-)  
> 
> ## Form letter - net-next-closed
> 
> The merge window for v6.18 has begun and therefore net-next is closed
> for new drivers, features, code refactoring and optimizations. We are
> currently accepting bug fixes only.
> 
> Please repost when net-next reopens after October 12th.
> 
> RFC patches sent for review only are obviously welcome at any time.

Oops sorry that is totally true and I forgot that we have entered the merge
window. Sorry for the noise :/

Regards,
-- 
Köry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

      reply	other threads:[~2025-09-30 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30  9:12 [PATCH net-next 0/3] Preserve PSE PD692x0 configuration across reboots Kory Maincent
2025-09-30  9:13 ` [PATCH net-next 1/3] net: pse-pd: pd692x0: Replace __free macro with explicit kfree calls Kory Maincent
2025-09-30  9:13 ` [PATCH net-next 2/3] net: pse-pd: pd692x0: Separate configuration parsing from hardware setup Kory Maincent
2025-09-30  9:13 ` [PATCH net-next 3/3] net: pse-pd: pd692x0: Preserve PSE configuration across reboots Kory Maincent
2025-09-30 14:40 ` [PATCH net-next 0/3] Preserve PSE PD692x0 " Paolo Abeni
2025-09-30 14:58   ` Kory Maincent [this message]

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=20250930165817.2e3e756d@kmaincent-XPS-13-7390 \
    --to=kory.maincent@bootlin.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dentproject@linuxfoundation.org \
    --cc=edumazet@google.com \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --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