linux-kernel - Re: [PATCH v3 0/2] arm64: dts: ti: k3-j7200-common-proc-board fixes

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: <168681817151.2098323.17529850133259185371.b4-ty@ti.com>
Date:   Thu, 15 Jun 2023 19:01:21 +0530
From:   Vignesh Raghavendra <vigneshr@...com>
To:     <linux-arm-kernel@...ts.infradead.org>, <afd@...com>, <bb@...com>,
        <vaishnav.a@...com>, <j-choudhary@...com>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <nm@...com>, <kristo@...nel.org>, <robh+dt@...nel.org>,
        <krzysztof.kozlowski+dt@...aro.org>, Udit Kumar <u-kumar1@...com>
CC:     Vignesh Raghavendra <vigneshr@...com>
Subject: Re: [PATCH v3 0/2] arm64: dts: ti: k3-j7200-common-proc-board fixes

Hi Udit Kumar,

On Wed, 19 Apr 2023 09:30:05 +0530, Udit Kumar wrote:
> This patch series fixes the pin mux configuration and enable
> wkup_i2c0 at board level.
> 
> Note to self: in u-boot i2c pin mux is set in R5 board file.
> which will moved to som file, Fix that too when syncing kernel
> and uboot DTS files.
> 
> [...]

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

[1/2] arm64: dts: ti: k3-j7200: Fix physical address of pin
      commit: 3d011933000ed9054c649952d83162d24f020a93
[2/2] arm64: dts: ti: k3-j7200-som: Enable I2C
      commit: 2f932d4151599bc647607ae841cf57273279168c

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