linux-kernel - Re: (subset) [PATCH v1 0/3] Fix incorrect bh2228fv compatible

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: <172131993701.119619.18261000113153693411.b4-ty@kernel.org>
Date: Thu, 18 Jul 2024 17:25:37 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-kernel@...r.kernel.org, Conor Dooley <conor@...nel.org>
Cc: Conor Dooley <conor.dooley@...rochip.com>, 
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, 
 Conor Dooley <conor+dt@...nel.org>, Shawn Guo <shawnguo@...nel.org>, 
 Sascha Hauer <s.hauer@...gutronix.de>, 
 Pengutronix Kernel Team <kernel@...gutronix.de>, 
 Fabio Estevam <festevam@...il.com>, Maxime Ripard <mripard@...nel.org>, 
 devicetree@...r.kernel.org, imx@...ts.linux.dev, 
 linux-arm-kernel@...ts.infradead.org, linux-spi@...r.kernel.org
Subject: Re: (subset) [PATCH v1 0/3] Fix incorrect bh2228fv compatible

On Wed, 17 Jul 2024 10:59:47 +0100, Conor Dooley wrote:
> Maxime made a typo when adding this device to the kernel all the way
> back in 2012, fix the spelling mistake.
> 
> Really this device should not be in trivial-devices.yaml, but I'm
> leaving the creation of a dedicated binding for when I get my hands on a
> device :smiling_imp:
> 
> [...]

Applied to

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

Thanks!

[1/3] dt-bindings: trivial-devices: fix Rohm BH2228FV compatible string
      commit: 5170dae5591036dba7daa519ea3126169300e275
[2/3] spi: spidev: add correct compatible for Rohm BH2228FV
      commit: fc28d1c1fe3b3e2fbc50834c8f73dda72f6af9fc

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