linux-kernel - Re: [PATCH] spi: remove spin_lock_irq and variable in the irq procress

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <165040834422.1910395.12598803243774889664.b4-ty@kernel.org>
Date:   Tue, 19 Apr 2022 23:45:44 +0100
From:   Mark Brown <broonie@...nel.org>
To:     lhjeff911@...il.com, linux-kernel@...r.kernel.org,
        linux-spi@...r.kernel.org
Cc:     wells.lu@...plus.com, nathan@...nel.org, trix@...hat.com,
        lh.kuo@...plus.com
Subject: Re: [PATCH] spi: remove spin_lock_irq and variable in the irq procress

On Fri, 15 Apr 2022 16:12:04 +0800, Li-hao Kuo wrote:
> remove spin_lock_irq spin_unlock_irq and variable in the irq funciton
> 
> 

Applied to

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

Thanks!

[1/1] spi: remove spin_lock_irq and variable in the irq procress
      commit: c81085840e03dd421532e16b22a8cde95de8ea41

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