From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Yury Norov <ynorov@caviumnetworks.com>
Cc: Madhavan Srinivasan <maddy@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Adrian Hunter <adrian.hunter@intel.com>,
Borislav Petkov <bp@suse.de>, David Ahern <dsahern@gmail.com>,
George Spelvin <linux@horizon.com>, Jiri Olsa <jolsa@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Wang Nan <wangnan0@huawei.com>, Yury Norov <yury.norov@gmail.com>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH] tools/perf: fix the word selected in find_*_bit
Date: Wed, 15 Jun 2016 18:29:58 -0300 [thread overview]
Message-ID: <20160615212958.GC4882@kernel.org> (raw)
In-Reply-To: <20160615211104.GA6978@yury-N73SV>
Em Thu, Jun 16, 2016 at 12:11:04AM +0300, Yury Norov escreveu:
> On Wed, Jun 15, 2016 at 10:51:27PM +0300, Yury Norov wrote:
> > Maybe there already is some macro doing the conversion for you...
>
> yes it is, cpu_to_le64() is what you want
Beware that the cpu_to_le64() in tools/perf is bogus, we need to grab a
copy from the kernel sources.
- Arnaldo
next prev parent reply other threads:[~2016-06-15 21:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 11:42 [PATCH] tools/perf: fix the word selected in find_*_bit Madhavan Srinivasan
2016-06-15 12:44 ` George Spelvin
2016-06-16 7:21 ` Madhavan Srinivasan
2016-06-15 19:51 ` Yury Norov
2016-06-15 21:11 ` Yury Norov
2016-06-15 21:29 ` Arnaldo Carvalho de Melo [this message]
2016-06-16 1:27 ` [PATCH] tools include: Fix wrong macro definitions for cpu_to_le* for big endian He Kuang
2016-06-16 1:32 ` He Kuang
2016-06-16 1:32 ` [PATCH 1/2] tools include: Sync byteorder/generic.h He Kuang
2016-06-16 6:39 ` Jiri Olsa
2016-06-16 1:32 ` [PATCH 2/2] tools include: Fix wrong macro definitions for cpu_to_le* for big endian He Kuang
2016-06-16 6:21 ` kbuild test robot
2016-06-16 6:39 ` Jiri Olsa
2016-06-16 1:35 ` [PATCH] tools/perf: fix the word selected in find_*_bit Hekuang
2016-06-16 13:11 ` Madhavan Srinivasan
2016-06-16 7:15 ` Madhavan Srinivasan
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=20160615212958.GC4882@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=bp@suse.de \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=linux@rasmusvillemoes.dk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.vnet.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=namhyung@kernel.org \
--cc=wangnan0@huawei.com \
--cc=ynorov@caviumnetworks.com \
--cc=yury.norov@gmail.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;
as well as URLs for NNTP newsgroup(s).