From: Will Deacon <will@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>,
Bhaskara Budiredla <bbudiredla@marvell.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] perf: MARVELL_CN10K_TAD_PMU should depend on ARCH_THUNDER
Date: Tue, 8 Feb 2022 16:21:52 +0000 [thread overview]
Message-ID: <164433205929.3624309.9655939450024180787.b4-ty@kernel.org> (raw)
In-Reply-To: <b4662a2c767d04cca19417e0c845edea2da262ad.1641995941.git.geert+renesas@glider.be>
On Wed, 12 Jan 2022 15:00:47 +0100, Geert Uytterhoeven wrote:
> The Marvell CN10K Last-Level cache Tag-and-data Units (LLC-TAD)
> performance monitor is only present on Marvell CN10K SoCs. Hence add a
> dependency on ARCH_THUNDER, to prevent asking the user about this driver
> when configuring a kernel without Cavium Thunder (incl. Marvell CN10K)
> SoC support.
>
>
> [...]
Applied to will (for-next/perf), thanks!
[1/1] perf: MARVELL_CN10K_TAD_PMU should depend on ARCH_THUNDER
https://git.kernel.org/will/c/e564518b0727
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Mark Rutland <mark.rutland@arm.com>,
Bhaskara Budiredla <bbudiredla@marvell.com>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] perf: MARVELL_CN10K_TAD_PMU should depend on ARCH_THUNDER
Date: Tue, 8 Feb 2022 16:21:52 +0000 [thread overview]
Message-ID: <164433205929.3624309.9655939450024180787.b4-ty@kernel.org> (raw)
In-Reply-To: <b4662a2c767d04cca19417e0c845edea2da262ad.1641995941.git.geert+renesas@glider.be>
On Wed, 12 Jan 2022 15:00:47 +0100, Geert Uytterhoeven wrote:
> The Marvell CN10K Last-Level cache Tag-and-data Units (LLC-TAD)
> performance monitor is only present on Marvell CN10K SoCs. Hence add a
> dependency on ARCH_THUNDER, to prevent asking the user about this driver
> when configuring a kernel without Cavium Thunder (incl. Marvell CN10K)
> SoC support.
>
>
> [...]
Applied to will (for-next/perf), thanks!
[1/1] perf: MARVELL_CN10K_TAD_PMU should depend on ARCH_THUNDER
https://git.kernel.org/will/c/e564518b0727
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-08 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 14:00 [PATCH] perf: MARVELL_CN10K_TAD_PMU should depend on ARCH_THUNDER Geert Uytterhoeven
2022-01-12 14:00 ` Geert Uytterhoeven
2022-02-08 16:21 ` Will Deacon [this message]
2022-02-08 16:21 ` Will Deacon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=164433205929.3624309.9655939450024180787.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=arnd@arndb.de \
--cc=bbudiredla@marvell.com \
--cc=catalin.marinas@arm.com \
--cc=geert+renesas@glider.be \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.