Re: [PATCH 0/3] Adding device tree and binding for Nvidia mgx cx8 switchboard

[Rob Herring <robh@kernel.org>]

On Fri, Aug 15, 2025 at 06:38:54PM -0500, Rob Herring (Arm) wrote:
> 
> On Fri, 15 Aug 2025 12:45:54 -0700, Marc Olberding wrote:
> > Patch 1 Adds the binding for the Nvidia mgx cx8 switchboard
> > Patch 2 Adds dtsi's for the mgx cx8 switchboard itself
> > Patch 3 Adds the dts for the mgx cx8 switchboard motherboard reference implementation.
> > 
> > This is an Aspeed AST2600 based reference implementation for a BMC
> > managing an Nvidia mgx cx8 switchboard. Dtsi files are broken out for
> > managing the mgx cx8 switchboard over i2c, so that others may reuse these
> > if they choose to implement their own board. There are two dtsi files
> > since the i2c topology is not symmetric between busses going to the mgx cx8
> > switchboard.
> > 
> > Reference to Ast2600 SoC [1].
> > 
> > Link: https://www.aspeedtech.com/server_ast2600/ [1]
> > 
> > 
> > Signed-off-by: Marc Olberding <molberding@nvidia.com>
> > ---
> > Marc Olberding (3):
> >       dt-bindings: arm: aspeed: Add Nvidia's mgx4u BMC
> >       ARM: dts: aspeed: Add device tree includes for the cx8 switchboard
> >       ARM: dts: aspeed: Add device tree for mgx4u BMC
> > 
> >  .../devicetree/bindings/arm/aspeed/aspeed.yaml     |    1 +
> >  arch/arm/boot/dts/aspeed/Makefile                  |    1 +
> >  .../boot/dts/aspeed/aspeed-bmc-nvidia-mgx4u.dts    | 1078 ++++++++++++++++++++
> >  .../dts/aspeed/nvidia-mgx-cx8-switch-north.dtsi    |   80 ++
> >  .../dts/aspeed/nvidia-mgx-cx8-switch-south.dtsi    |   80 ++
> >  5 files changed, 1240 insertions(+)
> > ---
> > base-commit: 7bac2c97af4078d7a627500c9bcdd5b033f97718

next-20250521!? Why are you using linux-next from 3 months ago?

Base your patches on the latest rc1 unless you have some dependency on 
post rc1 changes. Usually that means you need to base your tree on the 
maintainer's tree the series applies to (ASpeed in this case). 
The *current* linux-next is a shortcut for that.

Rob