linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Yicong Yang <yangyicong@huawei.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
	yangyicong@hisilicon.com, helgaas@kernel.org,
	lorenzo.pieralisi@arm.com, mathieu.poirier@linaro.org,
	suzuki.poulose@arm.com, jonathan.cameron@huawei.com,
	robin.murphy@arm.com, leo.yan@linaro.org, mark.rutland@arm.com,
	will@kernel.org, joro@8bytes.org,
	shameerali.kolothum.thodi@huawei.com, mingo@redhat.com,
	linux-kernel@vger.kernel.org, john.garry@huawei.com,
	linux-arm-kernel@lists.infradead.org, linux-pci@vger.kernel.org,
	linux-perf-users@vger.kernel.org,
	iommu@lists.linux-foundation.org, prime.zeng@huawei.com,
	liuqi115@huawei.com, james.clark@arm.com,
	zhangshaokun@hisilicon.com, linuxarm@huawei.com,
	alexander.shishkin@linux.intel.com, acme@kernel.org
Subject: Re: [PATCH v9 0/8] Add support for HiSilicon PCIe Tune and Trace device
Date: Mon, 27 Jun 2022 16:01:31 +0200	[thread overview]
Message-ID: <Yrm4O+AFbgnoBVba@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <e737393a-56dd-7d24-33d3-e935b14ba758@huawei.com>

On Mon, Jun 27, 2022 at 09:25:42PM +0800, Yicong Yang wrote:
> On 2022/6/27 21:12, Greg KH wrote:
> > On Mon, Jun 27, 2022 at 07:18:12PM +0800, Yicong Yang wrote:
> >> Hi Greg,
> >>
> >> Since the kernel side of this device has been reviewed for 8 versions with
> >> all comments addressed and no more comment since v9 posted in 5.19-rc1,
> >> is it ok to merge it first (for Patch 1-3 and 7-8)?
> > 
> > I am not the maintainer of this subsystem, so I do not understand why
> > you are asking me :(
> > 
> 
> I checked the log of drivers/hwtracing and seems patches of coresight/intel_th/stm
> applied by different maintainers and I see you applied some patches of intel_th/stm.
> Should any of these three maintainers or you can help applied this?

I was hoping Mark would have a look, since he knows this ARM stuff
better than me. But ISTR he's somewhat busy atm too. But an ACK from the
CoreSight people would also be appreciated.

And Arnaldo usually doesn't pick up the userspace perf bits until the
kernel side is sorted.

  reply	other threads:[~2022-06-27 14:02 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 11:55 [PATCH v9 0/8] Add support for HiSilicon PCIe Tune and Trace device Yicong Yang
2022-06-06 11:55 ` [PATCH v9 1/8] iommu/arm-smmu-v3: Make default domain type of HiSilicon PTT device to identity Yicong Yang
2022-06-06 11:55 ` [PATCH v9 2/8] hwtracing: hisi_ptt: Add trace function support for HiSilicon PCIe Tune and Trace device Yicong Yang
2022-07-07 17:59   ` Mathieu Poirier
2022-07-11 17:41   ` Mathieu Poirier
2022-07-11 17:46     ` Mathieu Poirier
2022-07-12 13:10     ` Yicong Yang
2022-06-06 11:55 ` [PATCH v9 3/8] hwtracing: hisi_ptt: Add tune " Yicong Yang
2022-06-06 11:55 ` [PATCH v9 4/8] perf tool: arm: Refactor event list iteration in auxtrace_record__init() Yicong Yang
2022-06-27  1:19   ` Leo Yan
2022-06-06 11:55 ` [PATCH v9 5/8] perf tool: Add support for HiSilicon PCIe Tune and Trace device driver Yicong Yang
2022-06-27  2:02   ` Leo Yan
2022-06-27  8:18     ` Yicong Yang
2022-06-06 11:55 ` [PATCH v9 6/8] perf tool: Add support for parsing HiSilicon PCIe Trace packet Yicong Yang
2022-06-06 11:55 ` [PATCH v9 7/8] docs: trace: Add HiSilicon PTT device driver documentation Yicong Yang
2022-07-06 17:57   ` Mathieu Poirier
2022-07-07 11:43     ` Yicong Yang
2022-07-07 16:20       ` Mathieu Poirier
2022-07-12 12:38         ` Yicong Yang
2022-07-12 15:02           ` Mathieu Poirier
2022-06-06 11:55 ` [PATCH v9 8/8] MAINTAINERS: Add maintainer for HiSilicon PTT driver Yicong Yang
2022-06-27 11:18 ` [PATCH v9 0/8] Add support for HiSilicon PCIe Tune and Trace device Yicong Yang
2022-06-27 13:12   ` Greg KH
2022-06-27 13:25     ` Yicong Yang
2022-06-27 14:01       ` Peter Zijlstra [this message]
2022-06-28  7:17         ` Yicong Yang
2022-06-29 16:43         ` Mathieu Poirier

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=Yrm4O+AFbgnoBVba@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=helgaas@kernel.org \
    --cc=iommu@lists.linux-foundation.org \
    --cc=james.clark@arm.com \
    --cc=john.garry@huawei.com \
    --cc=jonathan.cameron@huawei.com \
    --cc=joro@8bytes.org \
    --cc=leo.yan@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linuxarm@huawei.com \
    --cc=liuqi115@huawei.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=mathieu.poirier@linaro.org \
    --cc=mingo@redhat.com \
    --cc=prime.zeng@huawei.com \
    --cc=robin.murphy@arm.com \
    --cc=shameerali.kolothum.thodi@huawei.com \
    --cc=suzuki.poulose@arm.com \
    --cc=will@kernel.org \
    --cc=yangyicong@hisilicon.com \
    --cc=yangyicong@huawei.com \
    --cc=zhangshaokun@hisilicon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).