linux-kernel - Re: [PATCH] spi: Doc fix - Describe add_lock and dma_map_dev in spi

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: <165237312070.1053498.16178641624638760904.b4-ty@kernel.org>
Date:   Thu, 12 May 2022 17:32:00 +0100
From:   Mark Brown <broonie@...nel.org>
To:     sfr@...b.auug.org.au, skhan@...uxfoundation.org,
        siddhpant.gh@...il.com
Cc:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: Doc fix - Describe add_lock and dma_map_dev in spi_controller

On Thu, 12 May 2022 20:06:45 +0530, Siddh Raman Pant wrote:
> This fixes the corresponding warnings during building the docs.
> 
> 

Applied to

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

Thanks!

[1/1] spi: Doc fix - Describe add_lock and dma_map_dev in spi_controller
      commit: 75d6fe48a21a0ea1565228c12b9c16f3fb37b673

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