linux-kernel - Re: [PATCH v3 0/3] Improve SPI support for Ingenic SoCs.

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]

Date:   Mon, 25 Apr 2022 18:24:56 +0100
From:   Mark Brown <broonie@...nel.org>
To:     krzk+dt@...nel.org, zhouyanjie@...yeetech.com, robh+dt@...nel.org
Cc:     linux-spi@...r.kernel.org, sernia.zhou@...mail.com,
        dongsheng.qiu@...enic.com, contact@...ur-rojek.eu,
        reimu@...omaker.com, linux-mips@...r.kernel.org,
        zhenwenjin@...il.com, linux-kernel@...r.kernel.org,
        rick.tyliu@...enic.com, aric.pzqi@...enic.com,
        devicetree@...r.kernel.org, paul@...pouillou.net
Subject: Re: [PATCH v3 0/3] Improve SPI support for Ingenic SoCs.

On Sat, 23 Apr 2022 22:38:42 +0800, 周琰杰 (Zhou Yanjie) wrote:
> 1.Add support for using GPIOs as chip select lines on Ingenic SoCs.
> 2.Add support for probing the spi-ingenic driver on the JZ4775 SoC,
>   the X1000 SoC, and the X2000 SoC.
> 3.Modify annotation texts to be more in line with the current state.
> 
> v1->v2:
> Use "device_property_read_u32()" instead "of_property_read_u32()" as
> Paul Cercueil's suggestion.
> 
> [...]

Applied to

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

Thanks!

[1/3] SPI: Ingenic: Add support for use GPIO as chip select line.
      commit: e64e9ad267ca22ee3db6f9d7a02dc8400a23d4c8
[2/3] dt-bindings: SPI: Add bindings for new Ingenic SoCs.
      commit: aecec8bbb225965c6f775b946ad7bf40736c8f09
[3/3] SPI: Ingenic: Add support for new Ingenic SoCs.
      commit: 6d72b11403549a34b485d2fe323c8a57b4dd1958

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