From: Sudeep Holla <sudeep.holla@arm.com>
To: Jeremy Linton <jeremy.linton@arm.com>
Cc: mark.rutland@arm.com, catalin.marinas@arm.com,
rafael.j.wysocki@intel.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org, robert.moore@intel.com,
linux-acpi@vger.kernel.org, Sudeep Holla <sudeep.holla@arm.com>,
devel@acpica.org, erik.schmauss@intel.com,
linux-arm-kernel@lists.infradead.org, lenb@kernel.org
Subject: Re: [RFC 3/3] perf: arm_spe: Enable ACPI/Platform automatic module loading
Date: Mon, 11 Feb 2019 15:35:53 +0000 [thread overview]
Message-ID: <20190211153553.GB4792@e107155-lin> (raw)
In-Reply-To: <20190209004718.3292087-4-jeremy.linton@arm.com>
On Fri, Feb 08, 2019 at 06:47:18PM -0600, Jeremy Linton wrote:
> Lets add the MODULE_TABLE and platform id_table entries so that
> the SPE driver can attach to the ACPI platform device created by
> the core pmu code.
>
Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-02-11 15:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 0:47 [RFC 0/3] arm64: SPE ACPI enablement Jeremy Linton
2019-02-09 0:47 ` [RFC 1/3] ACPICA: ACPI 6.3: Add MADT/GICC/SPE extension Jeremy Linton
2019-02-11 18:27 ` Schmauss, Erik
2019-02-09 0:47 ` [RFC 2/3] arm_pmu: acpi: spe: Add initial MADT/SPE probing Jeremy Linton
2019-02-11 15:34 ` Sudeep Holla
2019-02-14 17:11 ` Will Deacon
2019-02-14 18:03 ` Jeremy Linton
2019-02-15 15:00 ` Will Deacon
2019-02-15 16:04 ` Jeremy Linton
2019-02-09 0:47 ` [RFC 3/3] perf: arm_spe: Enable ACPI/Platform automatic module loading Jeremy Linton
2019-02-11 15:35 ` Sudeep Holla [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=20190211153553.GB4792@e107155-lin \
--to=sudeep.holla@arm.com \
--cc=catalin.marinas@arm.com \
--cc=devel@acpica.org \
--cc=erik.schmauss@intel.com \
--cc=jeremy.linton@arm.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=mark.rutland@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=robert.moore@intel.com \
--cc=will.deacon@arm.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).