linux-kernel - Re: [PATCH] spi: Make of_register_spi

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <161903040535.13608.1822731950090796402.b4-ty@kernel.org>
Date:   Wed, 21 Apr 2021 20:03:26 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Charles Keepax <ckeepax@...nsource.cirrus.com>,
        saravanak@...gle.com
Cc:     Mark Brown <broonie@...nel.org>, linux-spi@...r.kernel.org,
        linux-kernel@...r.kernel.org, linus.walleij@...aro.org
Subject: Re: [PATCH] spi: Make of_register_spi_device also set the fwnode

On Wed, 21 Apr 2021 11:14:02 +0100, Charles Keepax wrote:
> Currently, the SPI core doesn't set the struct device fwnode pointer
> when it creates a new SPI device. This means when the device is
> registered the fwnode is NULL and the check in device_add which sets
> the fwnode->dev pointer is skipped. This wasn't previously an issue,
> however these two patches:
> 
> commit 4731210c09f5 ("gpiolib: Bind gpio_device to a driver to enable
> fw_devlink=on by default")
> commit ced2af419528 ("gpiolib: Don't probe gpio_device if it's not the
> primary device")
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: Make of_register_spi_device also set the fwnode
      commit: 0e793ba77c18382f08e440260fe72bc6fce2a3cb

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