linux-kernel - Re: [PATCH V6 0/3] spi: mediatek: add single/quad mode 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: <164915114188.276894.4149061684421416704.b4-ty@kernel.org>
Date:   Tue, 05 Apr 2022 10:32:21 +0100
From:   Mark Brown <broonie@...nel.org>
To:     leilk.liu@...iatek.com
Cc:     linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        robh+dt@...nel.org, linux-mediatek@...ts.infradead.org,
        linux-spi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        matthias.bgg@...il.com
Subject: Re: [PATCH V6 0/3] spi: mediatek: add single/quad mode support

On Mon, 21 Mar 2022 09:39:19 +0800, Leilk Liu wrote:
> This series of patches are based on spi for-next, and provide 3 patches to support MT7986.
> 
> V6:
>  1. remove SPI_CFG3_IPM_PIN_MODE_OFFSET.
>  2. add Reviewed-by: AngeloGioacchino Del Regno
> 
> V5:
>  1. remove 3 patches that already applied.
>  2. use devm_clk_get_optional.
>  3. remove of_mtk_spi_parse_dt()
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: mediatek: add spi memory support for ipm design
      commit: 9f763fd20da7d892ffaedac0c58d821922f8a674
[2/3] dt-bindings: spi: support hclk
      commit: a4765dfb80a7333aaac394a5ba20056d11b55636
[3/3] spi: mediatek: support hclk
      commit: a740f4e684c020ea57a8a198a9322d739f7ab6d5

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