linux-kernel - Re: [PATCH v2 0/2] Deprecate ti-serdes header file

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: <169028506508.1718716.4077417084454860962.b4-ty@ti.com>
Date:   Tue, 25 Jul 2023 06:38:03 -0500
From:   Nishanth Menon <nm@...com>
To:     <vigneshr@...com>, <kristo@...nel.org>, <robh+dt@...nel.org>,
        <krzysztof.kozlowski+dt@...aro.org>, <conor+dt@...nel.org>,
        <peda@...ntia.se>, <rogerq@...nel.org>,
        Jayesh Choudhary <j-choudhary@...com>
CC:     Nishanth Menon <nm@...com>, <s-vadapalli@...com>,
        <linux-arm-kernel@...ts.infradead.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/2] Deprecate ti-serdes header file

Hi Jayesh Choudhary,

On Fri, 21 Jul 2023 18:27:30 +0530, Jayesh Choudhary wrote:
> This series moves the ti-serdes.h header to arch/arm64/boot/dts/ti/
> as these constants do not have driver usage and are not suitable for
> bindings as discussed in [1].
> 
> Deprecating the bindings header for now instead of dropping them based
> on the discussion in [2].
> We expect to remove this bindings header in the next cycle.
> 
> [...]

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

[1/2] arm64: dts: ti: Use local header for SERDES MUX idle-state values
      commit: 8d08d7aac7f620b5d298fad0ba0e6e431ea132a9
[2/2] dt-bindings: ti-serdes-mux: Deprecate header with constants
      commit: 5438d75fb9d7bb863ddc5ef28b242ca50c9879ff

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] https://git.kernel.org/pub/scm/linux/kernel/git/ti/linux.git
-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D