linux-kernel - Re: (subset) [PATCH 1/5] spi: tegra210-quad: Fix combined sequence

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <166481567551.272308.1247948376003313434.b4-ty@kernel.org>
Date:   Mon, 03 Oct 2022 17:47:55 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Krishna Yarlagadda <kyarlagadda@...dia.com>,
        linux-tegra@...r.kernel.org, jonathanh@...dia.com,
        linux-spi@...r.kernel.org, thierry.reding@...il.com
Cc:     skomatineni@...dia.com, linux-kernel@...r.kernel.org,
        ldewangan@...dia.com
Subject: Re: (subset) [PATCH 1/5] spi: tegra210-quad: Fix combined sequence

On Sat, 1 Oct 2022 17:51:44 +0530, Krishna Yarlagadda wrote:
> Return value should be updated to zero in combined sequence routine
> if transfer is completed successfully. Currently it holds timeout value
> resulting in errors.
> 
> 

Applied to

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

Thanks!

[1/5] spi: tegra210-quad: Fix combined sequence
      commit: 8777dd9dff4020bba66654ec92e4b0ab6367ad30

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