linux-kernel - Re: (subset) [PATCH v2 0/2] lm70 and lm70llp doc link fixes

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: <171078286713.91354.1940130554038787719.b4-ty@kernel.org>
Date: Mon, 18 Mar 2024 17:27:47 +0000
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, 
 Kousik Sanagavarapu <five231003@...il.com>
Cc: linux-spi@...r.kernel.org, linux-hwmon@...r.kernel.org, 
 Jean Delvare <jdelvare@...e.com>, Guenter Roeck <linux@...ck-us.net>, 
 Shuah Khan <skhan@...uxfoundation.org>, 
 Javier Carrasco <javier.carrasco.cruz@...il.com>
Subject: Re: (subset) [PATCH v2 0/2] lm70 and lm70llp doc link fixes

On Mon, 18 Mar 2024 21:08:33 +0530, Kousik Sanagavarapu wrote:
> Fix links from the documentation and in-code comments pointing to
> datasheets.
> 
> Changes since v1:
> - I forgot to fix the links in in-code comments in spi, so do that.
> - New commit to address the same issues in hwmon/lm70 since the spi eval board
>   is based on that.
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: lm70llp: fix links in doc and comments
      commit: 7397175cb7b48f7a3fc699083aa46f1234904c7e

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