public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: patchwork-bot+netdevbpf@kernel.org, netdev@vger.kernel.org,
	conor.dooley@microchip.com,
	Valentina.FernandezAlanis@microchip.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, daire.mcnamara@microchip.com,
	pjw@kernel.org, palmer@dabbelt.com, aou@eecs.berkeley.edu,
	alex@ghiti.fr, nicolas.ferre@microchip.com,
	claudiu.beznea@tuxon.dev, richardcochran@gmail.com,
	samuel.holland@sifive.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	dave.stevenson@raspberrypi.com, sean.anderson@linux.dev,
	vineeth.karumanchi@amd.com, abin.joseph@amd.com,
	theo.lebrun@bootlin.com, Ryan.Wanner@microchip.com,
	haokexin@gmail.com
Subject: Re: [PATCH net-next v5 00/14] macb usrio/tsu patches
Date: Mon, 30 Mar 2026 17:20:29 +0100	[thread overview]
Message-ID: <20260330-repair-unclip-024a203a427d@spud> (raw)
In-Reply-To: <06a701dcc014$86def5b0$949ce110$@trustnetic.com>

[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

On Mon, Mar 30, 2026 at 03:12:10PM +0800, Jiawen Wu wrote:
> > Hello:
> > 
> > This series was applied to netdev/net-next.git (main)
> > by Jakub Kicinski <kuba@kernel.org>:
> > 
> > On Wed, 25 Mar 2026 16:28:04 +0000 you wrote:
> > > From: Conor Dooley <conor.dooley@microchip.com>
> > >
> > > Hey folks,
> > >
> > > At the very least, it'd be good of the soc vendor folks could check
> > > their platforms and see if their usrio stuff actually lines up with what
> > > the driver currently calls "macb_default_usrio". Ours didn't and it was
> > > a nasty surprise.
> > >
> > > [...]
> > 
> > Here is the summary with links:

> >   - [net-next,v5,02/14] net: macb: rename macb_default_usrio to at91_default_usrio as not all platforms have mii mode control in

> There are compilation errors after merging this patch set.
> I believe the error occurred where the CONFIG_OF is not set.

Thanks for the report. I have sent what's hopefully a fix..

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2026-03-30 16:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-25 16:28 [PATCH net-next v5 00/14] macb usrio/tsu patches Conor Dooley
2026-03-25 16:28 ` [PATCH net-next v5 01/14] Revert "net: macb: Clean up the .usrio settings in macb_config instances" Conor Dooley
2026-03-25 16:28 ` [PATCH net-next v5 02/14] net: macb: rename macb_default_usrio to at91_default_usrio as not all platforms have mii mode control in usrio Conor Dooley
2026-03-25 16:28 ` [PATCH net-next v5 03/14] net: macb: split USRIO_HAS_CLKEN capability in two Conor Dooley
2026-03-25 16:28 ` [PATCH net-next v5 04/14] dt-bindings: net: cdns,macb: replace cdns,refclk-ext with cdns,refclk-source Conor Dooley
2026-03-25 16:28 ` [PATCH net-next v5 05/14] net: macb: rework usrio refclk selection code Conor Dooley
2026-03-25 16:28 ` [PATCH net-next v5 06/14] net: macb: np4 doesn't need a usrio pointer Conor Dooley
2026-03-25 16:28 ` [PATCH net-next v5 07/14] net: macb: add mpfs specific usrio configuration Conor Dooley
2026-03-25 16:28 ` [PATCH net-next v5 08/14] net: macb: warn on pclk use as a tsu_clk fallback Conor Dooley
2026-03-25 16:28 ` [PATCH net-next v5 09/14] net: macb: clean up tsu clk rate acquisition Conor Dooley
2026-03-25 16:28 ` [PATCH net-next v5 10/14] dt-bindings: net: macb: add property indicating timer adjust mode Conor Dooley
2026-03-25 16:28 ` [PATCH net-next v5 11/14] net: macb: timer adjust mode is not supported Conor Dooley
2026-03-25 16:28 ` [PATCH net-next v5 12/14] net: macb: runtime detect MACB_CAPS_USRIO_DISABLED Conor Dooley
2026-03-25 16:28 ` [PATCH net-next v5 13/14] net: macb: set MACB_CAPS_USRIO_DISABLED if no usrio config is provided Conor Dooley
2026-03-25 16:28 ` [PATCH net-next v5 14/14] net: macb: drop usrio pointer on EyeQ5 config Conor Dooley
2026-03-29 21:40 ` [PATCH net-next v5 00/14] macb usrio/tsu patches patchwork-bot+netdevbpf
2026-03-30  7:12   ` Jiawen Wu
2026-03-30 16:20     ` Conor Dooley [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=20260330-repair-unclip-024a203a427d@spud \
    --to=conor@kernel.org \
    --cc=Ryan.Wanner@microchip.com \
    --cc=Valentina.FernandezAlanis@microchip.com \
    --cc=abin.joseph@amd.com \
    --cc=alex@ghiti.fr \
    --cc=andrew+netdev@lunn.ch \
    --cc=aou@eecs.berkeley.edu \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=daire.mcnamara@microchip.com \
    --cc=dave.stevenson@raspberrypi.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=edumazet@google.com \
    --cc=haokexin@gmail.com \
    --cc=jiawenwu@trustnetic.com \
    --cc=krzk+dt@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=nicolas.ferre@microchip.com \
    --cc=pabeni@redhat.com \
    --cc=palmer@dabbelt.com \
    --cc=patchwork-bot+netdevbpf@kernel.org \
    --cc=pjw@kernel.org \
    --cc=richardcochran@gmail.com \
    --cc=robh@kernel.org \
    --cc=samuel.holland@sifive.com \
    --cc=sean.anderson@linux.dev \
    --cc=theo.lebrun@bootlin.com \
    --cc=vineeth.karumanchi@amd.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