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: <170860805565.1966114.18241653060912010768.b4-ty@ti.com>
Date: Thu, 22 Feb 2024 18:58:07 +0530
From: Vignesh Raghavendra <vigneshr@...com>
To: <nm@...com>, <kristo@...nel.org>, <robh+dt@...nel.org>,
        <krzysztof.kozlowski+dt@...aro.org>, <sabiya.d@...tralsolutions.com>
CC: Vignesh Raghavendra <vigneshr@...com>, <devicetree@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
        <u-kumar1@...com>, Dasnavis Sabiya <sabiya.d@...com>
Subject: Re: [PATCH V3 0/2] Add CAN and OSPI support for AM69-SK platform

Hi sabiya.d@...tralsolutions.com,

On Tue, 20 Feb 2024 21:55:25 +0530, sabiya.d@...tralsolutions.com wrote:
> This series adds support for the below interfaces on AM69-SK platform:
> -  CAN support on both MCU and MAIN domains
> -  OSPI NOR flash support
> 
> v3: Changelog:
> 1) Updated OSPI partition table to increase the tiboot3 partition to 1MB.
> 2) Rebase the sources to accommodate the latest merge.
> 
> [...]

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

[1/2] arm64: dts: ti: k3-am69-sk: Enable CAN interfaces for AM69 SK board
      commit: daa2eb7f30eeb7127b6050e18f491326d278b836
[2/2] arm64: dts: ti: k3-am69-sk: Add support for OSPI flash
      commit: fabd934c6df2fb0c351144e424727fead261f333

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