On Mon, 12 Jan 2026 21:21:22 +0100, Andy Shevchenko wrote: > It seems all of the SPI drivers want to propagate fwnode (or of_node) > of the physical device to the SPI device. Make sure we don't duplicate > it over and over in each new driver (+2 in this cycle) by making core > to take care of that. Note, similar is done already by IIO and > I²C subsystems. > > There is one noticeable and quite specific case that is taken care in > the first patch and now we have a confirmation from Cirrus that everything > is okay. The rest is just a mechanical conversion after checking that > the parent device is assigned to the same that provides the respective > fwnode. > > [...]
Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/4] spi: Propagate default fwnode to the SPI controller device commit: f2d1a3318eb1ec860999db48cb8d13b43261624d [2/4] spi: Drop duplicate of_node assignment commit: 3974a585be78a1dc90a19d5cf1846a99954e3842 [3/4] spi: Drop duplicate fwnode assignment commit: 103c510e1c6832720059756d155dd13a42baa7ab [4/4] spi: Drop duplicate device_set_node() call commit: 37fbc1ab0f225d23f0839260a11375b4f1f7cf8c All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark
