mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: John <therealgraysky@proton.me>
Cc: jelonek.jonas@gmail.com, jonas@jonasjelonek.de,
	o.rempel@pengutronix.de, kory.maincent@bootlin.com,
	andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: pse-pd: realtek-pse-mcu: add RTL8238C device ID
Date: Thu, 19 Nov 2026 00:30:09 +0000	[thread overview]
Message-ID: <179504820977.2657179.13912428474327823978.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <EEsDzyK4pKqMZ9P6eCtfk5Qp2SXyprlFB4e4uQ7_O1iw3BuvnNm95DKBxuHy-mp3vdmUWhob9UWOzN9VWXoYyQIADqKPNvJt_gfaLaWpSkU=@proton.me>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sun, 15 Nov 2026 09:40:01 +0000 you wrote:
> From: John Audia <therealgraysky@proton.me>
> 
> Some Ubiquiti USW Pro Max 16 PoE units (boardrevision 3) carry a PSE
> MCU that reports device id 0x0238, so probe fails with "unknown PSE id
> 0x238". poemgr names this id RTL8238C.
> 
> The high byte of the id follows the chip revision, as with RTL8239
> (0x0039) and RTL8239C (0x0139), so add RTL8238C with the same power
> limits and power limit command as the RTL8238B (0x0138). Tested on such
> a unit, PoE works on all ports used.
> 
> [...]

Here is the summary with links:
  - [net-next] net: pse-pd: realtek-pse-mcu: add RTL8238C device ID
    https://git.kernel.org/netdev/net-next/c/48198bec8475

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-19  0:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-15  9:40 John
2026-11-16  9:40 ` netdev-bot+sashiko
2026-11-16  9:52 ` Kory Maincent
2026-11-16 12:00 ` Jonas Jelonek
2026-11-19  0:30 ` patchwork-bot+netdevbpf [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=179504820977.2657179.13912428474327823978.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=jelonek.jonas@gmail.com \
    --cc=jonas@jonasjelonek.de \
    --cc=kory.maincent@bootlin.com \
    --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=therealgraysky@proton.me \
    /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

all inboxes | Powered by JetHome®