From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Kan Liang <kan.liang@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
Vince Weaver <vincent.weaver@maine.edu>
Subject: Re: [PATCH] x86/perf/intel/rapl: Fix module name collision with powercap intel-rapl
Date: Fri, 8 Jul 2016 17:09:57 +0300 [thread overview]
Message-ID: <20160708140957.GT4329@intel.com> (raw)
In-Reply-To: <20160708132329.GA1640@gmail.com>
On Fri, Jul 08, 2016 at 03:23:29PM +0200, Ingo Molnar wrote:
>
> * Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
>
> > On Thu, Jun 23, 2016 at 06:06:49PM +0300, ville.syrjala@linux.intel.com wrote:
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > >
> > > Since commit 4b6e2571bf00 ("x86/perf/intel/rapl: Make the Intel RAPL PMU driver modular")
> > > the rapl perf module calls itself intel-rapl. That name was
> > > already in use by the rapl powercap driver, which now fails to
> > > load if the perf module is loaded. Fix the problem by renaming the
> > > perf module to intel-rapl-perf, so that both modules can coexist.
> >
> > Ping?
>
> It's in perf/urgent:
>
> # 175a20c16fdb x86/perf/intel/rapl: Fix module name collision with powercap intel-rapl
Cool. Thanks.
--
Ville Syrjälä
Intel OTC
prev parent reply other threads:[~2016-07-08 14:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 15:06 [PATCH] x86/perf/intel/rapl: Fix module name collision with powercap intel-rapl ville.syrjala
2016-07-06 9:04 ` Ville Syrjälä
2016-07-08 13:23 ` Ingo Molnar
2016-07-08 14:09 ` Ville Syrjälä [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=20160708140957.GT4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=acme@redhat.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vincent.weaver@maine.edu \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).