From: Paul Mackerras <paulus@samba.org>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>
Cc: benh@kernel.crashing.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, michael.neuling@au1.ibm.com
Subject: Re: [PATCH] powerpc, perf: Change PMU flag values representation from decimal to hex
Date: Fri, 16 Nov 2012 22:42:19 +1100 [thread overview]
Message-ID: <20121116114219.GA5745@bloggs.ozlabs.ibm.com> (raw)
In-Reply-To: <1353056344-1392-1-git-send-email-khandual@linux.vnet.ibm.com>
On Fri, Nov 16, 2012 at 02:29:04PM +0530, Anshuman Khandual wrote:
> Signed-off-by: Anshuman Khandual <khandual@linux.vnet.ibm.com>
That's not a sufficient description of why you are making this
change. In particular, what is the motivation for and impact of using
LONG_ASM_CONST?
Paul.
next prev parent reply other threads:[~2012-11-16 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 8:59 Anshuman Khandual
2012-11-16 11:42 ` Paul Mackerras [this message]
2012-11-19 6:15 ` Anshuman Khandual
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=20121116114219.GA5745@bloggs.ozlabs.ibm.com \
--to=paulus@samba.org \
--cc=benh@kernel.crashing.org \
--cc=khandual@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael.neuling@au1.ibm.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
all inboxes | Powered by JetHome®