From: Hekuang <hekuang@huawei.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
<alexander.shishkin@linux.intel.com>, <wangnan0@huawei.com>,
<adrian.hunter@intel.com>, <ak@linux.intel.com>,
<maddy@linux.vnet.ibm.com>, <bp@suse.de>, <dsahern@gmail.com>,
<linux@horizon.com>, <namhyung@kernel.org>,
<linux@rasmusvillemoes.dk>, <yury.norov@gmail.com>,
<mpe@ellerman.id.au>, <linux-kernel@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH v2 1/2] tools include: Adopt byte ordering macros from byteorder/generic.h
Date: Fri, 17 Jun 2016 09:50:10 +0800 [thread overview]
Message-ID: <57635752.6020201@huawei.com> (raw)
In-Reply-To: <20160616113600.GB20646@krava>
在 2016/6/16 19:36, Jiri Olsa 写道:
> On Thu, Jun 16, 2016 at 10:41:31AM +0000, He Kuang wrote:
>> From: Wang Nan <wangnan0@huawei.com>
>>
>> This patch adopts the macros for byte order conversion from
>> "include/linux/byteorder/generic.h" to
>> "tools/include/linux/byteorder/generic.h"
>>
>> tools/perf/MANIFEST is also updated for 'make perf-*-src-pkg'.
> other than explanation for the kbuild test robot email:
> http://marc.info/?l=linux-kernel&m=146605819924421&w=2
I think that's because of yesterday I sent these two patches
separately while the second one deponds on the first.
Thank you.
>
> it looks ok..
>
> jirka
>
prev parent reply other threads:[~2016-06-17 1:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-16 10:41 [PATCH v2 1/2] tools include: Adopt byte ordering macros from byteorder/generic.h He Kuang
2016-06-16 10:41 ` [PATCH v2 2/2] tools include: Fix wrong macro definitions for cpu_to_le* for big endian He Kuang
2016-06-16 11:36 ` [PATCH v2 1/2] tools include: Adopt byte ordering macros from byteorder/generic.h Jiri Olsa
2016-06-17 1:50 ` Hekuang [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=57635752.6020201@huawei.com \
--to=hekuang@huawei.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.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=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=wangnan0@huawei.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).