linux-kernel - Re: [PATCH v1 1/1] spi: Consistently use BIT for cs_index

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: <171326584478.1678604.5209919543907385015.b4-ty@kernel.org>
Date: Tue, 16 Apr 2024 20:10:44 +0900
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: [PATCH v1 1/1] spi: Consistently use BIT for cs_index_mask
 (part 2)

On Mon, 15 Apr 2024 21:47:57 +0300, Andy Shevchenko wrote:
> For some reason the commit 1209c5566f9b ("spi: Consistently use BIT
> for cs_index_mask") missed one place to change, do it here to finish
> the job.
> 
> 

Applied to

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

Thanks!

[1/1] spi: Consistently use BIT for cs_index_mask (part 2)
      commit: bb40996267670862544cb8e740afb77cbf3a7949

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