linux-kernel - Re: [PATCH v1 1/1] spi: nxp-fspi: Do not dereference fwnode in struct device

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: <166255652417.107207.11951981829518419145.b4-ty@kernel.org>
Date:   Wed, 07 Sep 2022 14:15:24 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Michael Walle <michael@...le.cc>, linux-kernel@...r.kernel.org,
        linux-spi@...r.kernel.org
Cc:     Han Xu <han.xu@....com>, Haibo Chen <haibo.chen@....com>,
        Yogesh Gaur <yogeshgaur.83@...il.com>
Subject: Re: [PATCH v1 1/1] spi: nxp-fspi: Do not dereference fwnode in struct device

On Tue, 6 Sep 2022 19:10:48 +0300, Andy Shevchenko wrote:
> 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