linux-kernel - Re: [PATCH 0/3] spi: add generic R-Car Gen4 and specific r8a779f0 support

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: <166194966864.85432.14716335347687736430.b4-ty@kernel.org>
Date:   Wed, 31 Aug 2022 13:41:08 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-renesas-soc@...r.kernel.org,
        Wolfram Sang <wsa+renesas@...g-engineering.com>
Cc:     linux-kernel@...r.kernel.org,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        linux-spi@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 0/3] spi: add generic R-Car Gen4 and specific r8a779f0 support

On Wed, 24 Aug 2022 11:43:23 +0200, Wolfram Sang wrote:
> Here are the patches to enable MSIOF on R-Car S4-8. They also introduce
> generic Gen4 support and move V3U to Gen4 (which it really is).
> 
> Wolfram Sang (3):
>   spi: renesas,sh-msiof: Add generic Gen4 and r8a779f0 support
>   spi: sh-msiof: add generic Gen4 binding
>   spi: renesas,sh-msiof: R-Car V3U is R-Car Gen4
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: renesas,sh-msiof: Add generic Gen4 and r8a779f0 support
      commit: e1e62f05d5d9d7726349e00562299d829e478ce9
[2/3] spi: sh-msiof: add generic Gen4 binding
      commit: ea9d001550abaf2f4c75cf4fcd936ea19f932b84
[3/3] spi: renesas,sh-msiof: R-Car V3U is R-Car Gen4
      commit: b076fdd02133e6a31db167f8acc368edc2530cc0

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