From: Peter Zijlstra <peterz@infradead.org>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: Re: [PATCH] perf tools: use ansi versions of asm and volatile
Date: Tue, 15 Oct 2013 13:15:51 +0200 [thread overview]
Message-ID: <20131015111551.GH10651@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1381833986-19393-1-git-send-email-artagnon@gmail.com>
On Tue, Oct 15, 2013 at 04:16:26PM +0530, Ramkumar Ramachandra wrote:
> asm and volatile are provided for backward compatibility; use the ansi
> versions __asm__ and __volatile__.
Also, you seem to have 'forgotten' to convert the 31 other instances :-)
# git grep -E "[[:space:]]asm[([:space:]]" tools/perf/ | wc -l
32
prev parent reply other threads:[~2013-10-15 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 10:46 [PATCH] perf tools: use ansi versions of asm and volatile Ramkumar Ramachandra
2013-10-15 11:04 ` Peter Zijlstra
2013-10-15 11:14 ` Ramkumar Ramachandra
2013-10-15 11:15 ` Peter Zijlstra [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=20131015111551.GH10651@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@ghostprotocols.net \
--cc=artagnon@gmail.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 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.