All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: <dave.jiang@intel.com>, <alison.schofield@intel.com>,
	<dan.j.williams@intel.com>, <ira.weiny@intel.com>,
	<fan.ni@samsung.com>, <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v2] perf/cxlpmu: Support missing events in 3.1 spec
Date: Wed, 16 Oct 2024 16:01:06 +0100	[thread overview]
Message-ID: <20241016160106.00004e34@Huawei.com> (raw)
In-Reply-To: <gghrbm3lt5wbjwhjrccmwercuvp6xy43mecqtezhkqznsctj5s@b2ntzbtyfehx>

On Wed, 9 Oct 2024 19:45:05 -0700
Davidlohr Bueso <dave@stgolabs.net> wrote:

> On Fri, 04 Oct 2024, Jonathan Cameron wrote:\n
> 
> >Driver is in perf though so you need to +CC perf maintainers as
> >they will probably pick this up directly.  
> 
> Doing the v3 to add the typo Alison pointed out, I remembered
> why I didn't Cc a perf list. Which is it? it is not clear to me
> exactly who is responsible to pick this up outside of the cxl
> world:
> 
> $ ./scripts/get_maintainer.pl 0001-perf-cxlpmu-Support-missing-events-in-3.1-spec.patch
> Jonathan Cameron <jonathan.cameron@huawei.com> (maintainer:COMPUTE EXPRESS LINK PMU (CPMU))
> Will Deacon <will@kernel.org> (maintainer:ARM PMU PROFILING AND DEBUGGING)
> Mark Rutland <mark.rutland@arm.com> (maintainer:ARM PMU PROFILING AND DEBUGGING)
> linux-cxl@vger.kernel.org (open list:COMPUTE EXPRESS LINK PMU (CPMU))
> linux-arm-kernel@lists.infradead.org (moderated list:ARM PMU PROFILING AND DEBUGGING)
> linux-kernel@vger.kernel.org (open list)
> 
> ... Yeah I guess it's Will and Mark, but arm seems really
> misleading and out of place for this. Imo both the cxl driver
> and pmu code should have the same maintainer scope.

There was a discussion ages ago about changing that maintainer entry
to make it more generic (drivers/perf).  With a few exceptions the reality
is that Will and Mark end up reviewing everything in there :)

Generally for PMU drivers the perf specific aspects end up more complex
than the hardware side. That's why we put the driver in drivers/perf.

I don't think either Mark / Will / CXL maintainers really care a lot
about who does the patch wrangling on simple patches like this beyond
if it is from perf side no one wonders what the CXL maintainers are doing
touching code in drivers/perf.

Jonathan


> 
> But even if this does not change, I think the maintainer entries
> should at least be labeled something more generic.
> 
> Thanks,
> Davidlohr


  reply	other threads:[~2024-10-16 15:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30 20:34 [PATCH v2] perf/cxlpmu: Support missing events in 3.1 spec Davidlohr Bueso
2024-10-04 11:44 ` Jonathan Cameron
2024-10-10  2:45   ` Davidlohr Bueso
2024-10-16 15:01     ` Jonathan Cameron [this message]
2024-10-04 16:43 ` Alison Schofield

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=20241016160106.00004e34@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=alison.schofield@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=fan.ni@samsung.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.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 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.