[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <161131975585.21423.9075334839139359625.b4-ty@ti.com>
Date: Fri, 22 Jan 2021 06:49:53 -0600
From: Nishanth Menon <nm@...com>
To: Dave Gerlach <d-gerlach@...com>, Suman Anna <s-anna@...com>,
Nishanth Menon <nm@...com>, Sudeep Holla <sudeep.holla@....com>
CC: Tero Kristo <kristo@...nel.org>, <linux-kernel@...r.kernel.org>,
<devicetree@...r.kernel.org>, Rob Herring <robh+dt@...nel.org>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH] arm64: dts: ti: k3*: Fixup PMU compatibility to be CPU specific
On Wed, 20 Jan 2021 13:51:45 -0600, Nishanth Menon wrote:
> We can use CPU specific pmu configuration to expose the appropriate
> CPU specific events rather than just the basic generic pmuv3 perf
> events.
Hi Nishanth Menon,
I have applied the following to branch ti-k3-dts-next on [1].
Thank you!
[1/1] arm64: dts: ti: k3*: Fixup PMU compatibility to be CPU specific
commit: c72bf319f12803d8c8ddc3dbf54927380fc65b50
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] git://git.kernel.org/pub/scm/linux/kernel/git/nmenon/linux.git
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
Powered by blists - more mailing lists