From: Peter Zijlstra <peterz@infradead.org>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Mischa Jonker <Mischa.Jonker@synopsys.com>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
James Hogan <james.hogan@imgtec.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: add const qualifier to perf_pmu_register's 'name' arg
Date: Tue, 4 Jun 2013 13:03:14 +0200 [thread overview]
Message-ID: <20130604110314.GN8923@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <51ADBB1D.9060805@synopsys.com>
On Tue, Jun 04, 2013 at 03:32:05PM +0530, Vineet Gupta wrote:
> On 06/04/2013 03:28 PM, Peter Zijlstra wrote:
> > On Tue, Jun 04, 2013 at 11:45:48AM +0200, Mischa Jonker wrote:
> >> This allows us to use pdev->name for registering a PMU device.
> >> IMO the name is not supposed to be changed anyway.
> >>
> > Indeed, and thanks!
> >
> > PS. WTH is a metag?
>
> It's the cpu core from Imagination Tech - their port got merged in 3.9 (along with
> ARC from Synopsys).
So its Meta-G, not me-tag :-) Google gave me the below, its not exactly
clear what kind of animal it is or what the G stands for. Too much
marketing speak, too little useful information.
http://www.imgtec.com/meta/meta-technology.asp
Simlar 'complaint' for the ARC stuff really, only marketing speak :-)
next prev parent reply other threads:[~2013-06-04 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 9:45 [PATCH] perf: add const qualifier to perf_pmu_register's 'name' arg Mischa Jonker
2013-06-04 9:58 ` Peter Zijlstra
2013-06-04 10:02 ` Vineet Gupta
2013-06-04 11:03 ` Peter Zijlstra [this message]
2013-06-04 11:09 ` Vineet Gupta
2013-06-04 11:18 ` Peter Zijlstra
2013-06-12 11:49 ` James Hogan
2013-06-19 18:38 ` [tip:perf/core] perf: Add " tip-bot for Mischa Jonker
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=20130604110314.GN8923@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Mischa.Jonker@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=acme@ghostprotocols.net \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.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