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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <163955230562.15251.11883711226345772344.b4-ty@ti.com>
Date:   Wed, 15 Dec 2021 12:42:24 +0530
From:   Vignesh Raghavendra <vigneshr@...com>
To:     <nm@...com>, Jayesh Choudhary <j-choudhary@...com>
CC:     Vignesh Raghavendra <vigneshr@...com>, <kristo@...nel.org>,
        <robh+dt@...nel.org>, <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>, <jan.kiszka@...mens.com>,
        <devicetree@...r.kernel.org>
Subject: Re: [PATCH] arm64: dts: ti: iot2050: Disable mcasp nodes at dtsi level

Hi Jayesh Choudhary,
 
On Wed, 17 Nov 2021 11:08:06 +0530, Jayesh Choudhary wrote:
> Disable mcasp nodes 0-2 because several required properties
> are not present in the dtsi file as they are board specific.
> These nodes can be enabled via an overlay whenever required.
> 
> 
 
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
 
[1/1] arm64: dts: ti: iot2050: Disable mcasp nodes at dtsi level
      commit: 277ee96f89d806f110e3011ea324155dd69e798f
 
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
--
Vignesh

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ