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: <168682555626.2264847.7193857222855659588.b4-ty@ti.com>
Date:   Thu, 15 Jun 2023 16:09:27 +0530
From:   Vignesh Raghavendra <vigneshr@...com>
To:     <linux-kernel@...r.kernel.org>, <devicetree@...r.kernel.org>,
        Bhavya Kapoor <b-kapoor@...com>
CC:     Vignesh Raghavendra <vigneshr@...com>,
        <linux-arm-kernel@...ts.infradead.org>,
        <krzysztof.kozlowski+dt@...aro.org>, <robh+dt@...nel.org>,
        <kristo@...nel.org>, <nm@...com>
Subject: Re: [PATCH v2 0/2] arm64: dts: ti: k3-j784s4: Add support for ADC nodes

Hi Bhavya Kapoor,

On Tue, 02 May 2023 13:41:15 +0530, Bhavya Kapoor wrote:
> J784S4 has two instances of 8 channel ADCs in MCU domain. Add support
> for both ADC nodes in dtsi file. Add pinmux information for both
> instances of ADC in board dts file.
> 
> Link to v1 -> https://lore.kernel.org/all/0f553758-c2cc-ce70-47e0-99e08c2d94a1@ti.com/
> 
> Changelog v1->v2 :
> - Modified indentation according to Vignesh's Comments
> 
> [...]

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

[1/2] arm64: dts: ti: k3-j784s4-mcu-wakeup: Add support for ADC nodes
      commit: ad5f7c514442a5eb29a415f75b3ea2744933e274
[2/2] arm64: dts: ti: k3-j784s4-evm: Add pinmux information for ADC
      commit: e99913ad58af3172343e3b22fa7a2a794d78b8c1

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