From: Mark Rutland <mark.rutland@arm.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Russell King <linux@armlinux.org.uk>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] drivers: perf: arm_pmu: Drop 'pmu_lock' element from 'struct pmu_hw_events'
Date: Mon, 4 Dec 2023 09:48:09 +0000 [thread overview]
Message-ID: <ZW2gWTfIKgHAYwSd@FVFF77S0Q05N> (raw)
In-Reply-To: <a8362015-c6e6-4d59-ba2b-67dc12bd89c8@arm.com>
On Tue, Nov 28, 2023 at 10:59:49AM +0530, Anshuman Khandual wrote:
>
>
> On 11/15/23 14:58, Anshuman Khandual wrote:
> > This series drops 'pmu_lock' usage from all arm platforms which had already
> > been dropped from arm64 platforms earlier via the following commit.
> >
> > commit 2a0e2a02e4b7 ("arm64: perf: Remove PMU locking").
> >
> > Afterwards, drop unused 'pmu_lock' element from 'struct pmu_hw_events'. The
> > series applies on 6.7-rc1 and has been tested on arm64. Although just build
> > tested for arm platform.
> >
> > Cc: Mark Rutland <mark.rutland@arm.com>
> > Cc: Will Deacon <will@kernel.org>
> > Cc: Russell King <linux@armlinux.org.uk>
> > Cc: linux-perf-users@vger.kernel.org
> > Cc: linux-kernel@vger.kernel.org
> > Cc: linux-arm-kernel@lists.infradead.org
> >
> > Changes in V1:
> >
> > - Added some build warning fixes
>
> Hello Will/Mark,
>
> Any updates or concerns on this series ?
The changes themselves look good to me. I'd like to tweak the commit message
for the first patch (and I've given specific wording that we can use).
Will, are you happy to fold that in when applying, or would you prefer that
Anshuman sends a v2?
Mark.
_______________________________________________
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:[~2023-12-04 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 9:28 [PATCH 0/2] drivers: perf: arm_pmu: Drop 'pmu_lock' element from 'struct pmu_hw_events' Anshuman Khandual
2023-11-15 9:28 ` [PATCH 1/2] arm: perf: Remove PMU locking Anshuman Khandual
2023-12-04 9:45 ` Mark Rutland
2023-11-15 9:28 ` [PATCH 2/2] drivers: perf: arm_pmu: Drop 'pmu_lock' element from 'struct pmu_hw_events' Anshuman Khandual
2023-12-04 9:45 ` Mark Rutland
2023-11-28 5:29 ` [PATCH 0/2] " Anshuman Khandual
2023-12-04 9:48 ` Mark Rutland [this message]
2023-12-05 15:16 ` 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=ZW2gWTfIKgHAYwSd@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=anshuman.khandual@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=will@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox