Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:7 as permitted sender) client-ip=2620:137:e000::3:7;
From:   Will Deacon <will@kernel.org>
To:     robin.murphy@arm.com, catalin.marinas@arm.com,
        suzuki.poulose@arm.com, ilkka@os.amperecomputing.com,
        Besar Wicaksono <bwicaksono@nvidia.com>, mark.rutland@arm.com
Cc:     kernel-team@android.com, Will Deacon <will@kernel.org>,
        jonathanh@nvidia.com, rwiley@nvidia.com,
        linux-arm-kernel@lists.infradead.org, efunsten@nvidia.com,
        linux-kernel@vger.kernel.org, treding@nvidia.com,
        linux-tegra@vger.kernel.org, vsethi@nvidia.com
Subject: Re: [PATCH v6] perf: arm_cspmu: Separate Arm and vendor module
Date:   Mon,  9 Oct 2023 17:56:42 +0100
Message-Id: <169651070763.1133315.8714234562874350620.b4-ty@kernel.org>
In-Reply-To: <20230821231608.50911-1-bwicaksono@nvidia.com>
References: <20230821231608.50911-1-bwicaksono@nvidia.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 21 Aug 2023 18:16:08 -0500, Besar Wicaksono wrote:
> Arm Coresight PMU driver consists of main standard code and
> vendor backend code. Both are currently built as a single module.
> This patch adds vendor registration API to separate the two to
> keep things modular. The main driver requests each known backend
> module during initialization and defer device binding process.
> The backend module then registers an init callback to the main
> driver and continue the device driver binding process.
> 
> [...]

Applied to will (for-next/perf), thanks!

[1/1] perf: arm_cspmu: Separate Arm and vendor module
      https://git.kernel.org/will/c/bfc653aa89cb

Cheers,
-- 
Will

https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev