From: Will Deacon <will.deacon@arm.com>
To: Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
linux-pci@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
Shaokun Zhang <zhangshaokun@hisilicon.com>,
linuxarm@huawei.com, Keith Busch <keith.busch@intel.com>,
Zhou Wang <wangzhou1@hisilicon.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
linux-arm-kernel@lists.infradead.org,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
alex.umansky@huawei.com, Eric.Wehage@huawei.com,
Logan Gunthorpe <logang@deltatee.com>
Subject: Re: [RFC PATCH 2/2] PCI/portdrv Hisilicon PCIe transport layer Port PMU driver.
Date: Thu, 3 Jan 2019 15:44:40 +0000 [thread overview]
Message-ID: <20190103154439.GC16311@edgewater-inn.cambridge.arm.com> (raw)
In-Reply-To: <20181218102127.0000018e@huawei.com>
On Tue, Dec 18, 2018 at 10:21:27AM +0000, Jonathan Cameron wrote:
> On Mon, 17 Dec 2018 12:19:15 -0600
> Bjorn Helgaas <helgaas@kernel.org> wrote:
> > Agreed. I could imagine a drivers/pci/pmu/ directory sort of like
> > drivers/pci/switch/.
>
> That might work. Mark, Will what do you think? As long as you and Bjorn
> agree I don't think it'll really matter which one is chosen.
>
> driver/pci/pmu/ or drivers/perf/pci ?
I have a slight preference for the latter since the perf interface for
PMU drivers is notoriously subtle and error-prone. Keeping PMU drivers
together can be helpful to spot emerging patterns and makes cross-driver
changes easier to co-ordinate.
However, I'll defer to Bjorn since it's only a minor preference. We'd
obviously loop in linux-pci + Bjorn on any new submissions.
Will
prev parent reply other threads:[~2019-01-03 15:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20181214131055.52253-1-Jonathan.Cameron@huawei.com>
[not found] ` <20181214131055.52253-3-Jonathan.Cameron@huawei.com>
2018-12-14 23:55 ` Bjorn Helgaas
2018-12-17 11:09 ` Jonathan Cameron
2018-12-17 18:19 ` Bjorn Helgaas
2018-12-17 18:34 ` Logan Gunthorpe
2018-12-18 10:21 ` Jonathan Cameron
2019-01-03 15:44 ` Will Deacon [this message]
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=20190103154439.GC16311@edgewater-inn.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=Eric.Wehage@huawei.com \
--cc=alex.umansky@huawei.com \
--cc=helgaas@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=keith.busch@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=logang@deltatee.com \
--cc=mark.rutland@arm.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
--cc=wangzhou1@hisilicon.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
all inboxes | Powered by JetHome®