linux-kernel - Re: [PATCH 1/2] spi: pl022: delete description of cur

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: <170265761567.87261.2454124954064239265.b4-ty@kernel.org>
Date: Fri, 15 Dec 2023 16:26:55 +0000
From: Mark Brown <broonie@...nel.org>
To: linus.walleij@...aro.org, linux-arm-kernel@...ts.infradead.org, 
 linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Nam Cao <namcao@...utronix.de>
Cc: kernel test robot <lkp@...el.com>
Subject: Re: [PATCH 1/2] spi: pl022: delete description of cur_msg

On Fri, 15 Dec 2023 12:33:37 +0100, Nam Cao wrote:
> The variable cur_msg was removed, but its description is left behind.
> Delete this description.
> 
> 

Applied to

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

Thanks!

[1/2] spi: pl022: delete description of cur_msg
      commit: e695c1fc5a3db1e161abe8061d715a504aff3f9f
[2/2] spi: pl022: update description of internal_cs_control()
      commit: 644f315d12ea29a67bc985d06ab0962452eb3605

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