linux-kernel - Re: [PATCH] spi: tegra210-quad: Fix duplicate resource error

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: <166868571080.694164.9085397886273331587.b4-ty@kernel.org>
Date:   Thu, 17 Nov 2022 11:48:30 +0000
From:   Mark Brown <broonie@...nel.org>
To:     jonathanh@...dia.com, Krishna Yarlagadda <kyarlagadda@...dia.com>,
        linux-tegra@...r.kernel.org, linux-spi@...r.kernel.org,
        thierry.reding@...il.com
Cc:     ldewangan@...dia.com, linux-kernel@...r.kernel.org,
        skomatineni@...dia.com
Subject: Re: [PATCH] spi: tegra210-quad: Fix duplicate resource error

On Thu, 17 Nov 2022 12:33:20 +0530, Krishna Yarlagadda wrote:
> controller data alloc is done with client device data causing duplicate
> resource error. Allocate memory using controller device when using devm
> 
> Fixes: f89d2cc3967a ("spi: tegra210-quad: use devm call for cdata memory")
> 
> 

Applied to

   broonie/spi.git for-next

Thanks!

[1/1] spi: tegra210-quad: Fix duplicate resource error
      commit: 2197aa6b0aa236b9896a09b9d08d6924d18b84f6

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