From: James Hogan <james.hogan@imgtec.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Vineet Gupta <Vineet.Gupta1@synopsys.com>,
Mischa Jonker <Mischa.Jonker@synopsys.com>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf: add const qualifier to perf_pmu_register's 'name' arg
Date: Wed, 12 Jun 2013 12:49:46 +0100 [thread overview]
Message-ID: <51B8605A.60402@imgtec.com> (raw)
In-Reply-To: <20130604111816.GP8923@twins.programming.kicks-ass.net>
On 04/06/13 12:18, Peter Zijlstra wrote:
> On Tue, Jun 04, 2013 at 04:39:05PM +0530, Vineet Gupta wrote:
>> On 06/04/2013 04:33 PM, Peter Zijlstra wrote:
>>> Simlar 'complaint' for the ARC stuff really, only marketing speak :-)
>>
>> You mean lack of prefix in this case (as opposed to MetaG).
>
> Nah, lack of proper (!markting speak) introduction to the arch ;-)
>
> Is there something like the Intel SDM for these archs,
For metag, see the patchset intro for a brief (hopefully !marketing)
intro and links to documentation. Meta is the marketing name, metag is
generally used in code which reduces ambiguity with the word meta - tbh
I'm not certain whether metag is short for metagence or means something
else, but it's been that way for years now.
http://lwn.net/Articles/534906/
> if so, do we want
> to make it easier to find them for people?
Where would you suggest?
Some other arches link to the linux-$ARCH project homepages in Kconfig
help text which makes sense as that can then link to various
documentation and be more easily kept up to date. Not all arches have a
big project around them like that though.
Cheers
James
next prev parent reply other threads:[~2013-06-12 11:49 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
2013-06-04 11:09 ` Vineet Gupta
2013-06-04 11:18 ` Peter Zijlstra
2013-06-12 11:49 ` James Hogan [this message]
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=51B8605A.60402@imgtec.com \
--to=james.hogan@imgtec.com \
--cc=Mischa.Jonker@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.