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  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:   Tue, 5 Oct 2021 17:59:09 -0500
From:   Nishanth Menon <>
To:     Jan Kiszka <>, Tero Kristo <>,
        Rob Herring <>
CC:     Nishanth Menon <>, <>,
        Chao Zeng <>,
        Bao Cheng Su <>
Subject: Re: [PATCH v5 0/6] arm64: dts: Update IOT2050 boards

On Sun, 26 Sep 2021 14:05:11 +0200, Jan Kiszka wrote:
> This enhances the DTs for the IOT2050, primarily by added support for
> upcoming Production Generation 2 (PG2) and by ordering the MMC devices
> consistently across variants.
> Changes in v5:
>  - fix usb0 node (for true USB 3.0 support)
>  - added reviewed/acked tags
> [...]

Hi Jan Kiszka,

I have applied the following to branch ti-k3-dts-next on [1].
Thank you!

[1/6] arm64: dts: ti: iot2050: Flip mmc device ordering on Advanced devices
      commit: 06784f7679274be3ca170a689c56192143a04541
[2/6] arm64: dts: ti: iot2050: Disable SR2.0-only PRUs
      commit: 262a98b43c2a08a5446bab2030f8fb68d3699396
[3/6] arm64: dts: ti: iot2050: Add/enabled mailboxes and carve-outs for R5F cores
      commit: af755fe2b36c87abfa6f00caf7dfce6351b7412a
[4/6] dt-bindings: arm: ti: Add bindings for Siemens IOT2050 PG2 boards
      commit: 4f535a0e38f696cadc92cc980d25a4198b11ae33
[5/6] arm64: dts: ti: iot2050: Prepare for adding 2nd-generation boards
      commit: a9dbf044c600277f5d2805831a73083f3688e19f
[6/6] arm64: dts: ti: iot2050: Add support for product generation 2 boards
      commit: 614d47cc9303893c706c0c94516249eb3adaeb80

Side note:
- There are still cleanups that are in works (tsadc, cdns, etc..) - since
  these are already present and active cleanup is going on, letting it past,
  but if I do get a push back from upstream maintainers, I'd have to pull the
  series back.

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent up the chain during
the next merge window (or sooner if it is a relevant 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.

[1] git://
Nishanth Menon
Key (0xDDB5849D1736249D)/Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

Powered by blists - more mailing lists