spi: nxp-fspi: Do not dereference fwnode in struct device
Subsystems (2)
PATCH 1/1 spi: nxp-fspi: Do not dereference fwnode in struct device
In order to make the underneath API easier to change in the future, prevent users from dereferencing fwnode from struct device. Instead, use the specific dev_fwnode() API for that.
--- drivers/spi/spi-nxp-fspi.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/spi/spi-nxp-fspi.c +4 -4
@@ -588,7 +588,7 @@ static int nxp_fspi_clk_prep_enable(struct nxp_fspi *f) {int ret; -if (is_acpi_node (f->dev->fwnode)) +if (is_acpi_node (dev_fwnode (f->dev)))return 0 ; ret =clk_prepare_enable (f->clk_en);
@@ -606,7 +606,7 @@ static int nxp_fspi_clk_prep_enable(struct nxp_fspi *f)static int nxp_fspi_clk_disable_unprep (struct nxp_fspi *f) { -if (is_acpi_node (f->dev->fwnode)) +if (is_acpi_node (dev_fwnode (f->dev)))return 0 ;clk_disable_unprepare (f->clk);
@@ -1100,7 +1100,7 @@ static int nxp_fspi_probe(struct platform_device *pdev)platform_set_drvdata (pdev, f);/* find the resources - configuration register address space */ -if (is_acpi_node (f->dev->fwnode)) +if (is_acpi_node (dev_fwnode (f->dev))) res =platform_get_resource (pdev,IORESOURCE_MEM ,0 );else res = platform_get_resource_byname(pdev,
@@ -1113,7 +1113,7 @@ static int nxp_fspi_probe(struct platform_device *pdev) }/* find the resources - controller memory mapped space */ -if (is_acpi_node (f->dev->fwnode)) +if (is_acpi_node (dev_fwnode (f->dev))) res =platform_get_resource (pdev,IORESOURCE_MEM ,1 );else res = platform_get_resource_byname(pdev,
Signature · 1 line
2.35.1
Mark Brown
maintainerQuoted 5 lines · Andy Shevchenko
In order to make the underneath API easier to change in the future, prevent users from dereferencing fwnode from struct device. Instead, use the specific
dev_fwnode()API for that.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] spi: nxp-fspi: Do not dereference fwnode in struct device
commit: 4b9ef436383e8aa910b71927b3f25ede9b190707
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