linux-kernel - Re: [PATCH 1/2] drm/etnaviv: Expose a few more chipspecs to userspace

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <170490387684.1887297.10058632363349793019.b4-ty@linaro.org>
Date: Wed, 10 Jan 2024 17:24:36 +0100
From: Neil Armstrong <neil.armstrong@...aro.org>
To: Tomeu Vizoso <tomeu@...euvizoso.net>
Cc: Christian Gmeiner <cgmeiner@...lia.com>, 
 Lucas Stach <l.stach@...gutronix.de>, 
 Russell King <linux+etnaviv@...linux.org.uk>, 
 Christian Gmeiner <christian.gmeiner@...il.com>, 
 David Airlie <airlied@...il.com>, Daniel Vetter <daniel@...ll.ch>, 
 Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>, 
 Maxime Ripard <mripard@...nel.org>, Thomas Zimmermann <tzimmermann@...e.de>, 
 etnaviv@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org, 
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] drm/etnaviv: Expose a few more chipspecs to
 userspace

Hi,

On Wed, 10 Jan 2024 16:37:00 +0100, Tomeu Vizoso wrote:
> These ones will be needed to make use fo the NN and TP units in the NPUs
> based on Vivante IP.
> 
> 

Thanks, Applied to https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git (v6.9/arm64-dt)

[1/2] drm/etnaviv: Expose a few more chipspecs to userspace
      (no commit info)
[2/2] arm64: dts: amlogic: meson-g12-common: Set the rates of the clocks for the NPU
      https://git.kernel.org/amlogic/c/507b3e756ffcb174d383dd05df5084aed9bb6d14

These changes has been applied on the intermediate git tree [1].

The v6.9/arm64-dt branch will then be sent via a formal Pull Request to the Linux SoC maintainers
for inclusion in their intermediate git branches in order to be sent to Linus during
the next merge window, or sooner if it's a set of fixes.

In the cases of fixes, those will be merged in the current release candidate
kernel and as soon they appear on the Linux master branch they will be
backported to the previous Stable and Long-Stable kernels [2].

The intermediate git branches are merged daily in the linux-next tree [3],
people are encouraged testing these pre-release kernels and report issues on the
relevant mailing-lists.

If problems are discovered on those changes, please submit a signed-off-by revert
patch followed by a corrective changeset.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git
[2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
[3] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git

-- 
Neil