From: Irina Tirdea <irina.tirdea@gmail.com>
To: David Ahern <dsahern@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 03/13] perf tools: drop asm/byteorder.h wrapper
Date: Sun, 2 Sep 2012 22:58:02 +0300 [thread overview]
Message-ID: <CANg8OWKK7dgc46ddaZddhJGeTT_GWS7Swn2czTsrk+yP65tM1g@mail.gmail.com> (raw)
In-Reply-To: <503E411D.2040406@gmail.com>
> This https://lkml.org/lkml/2012/8/29/150 should fix the netinet/tcp.h build
> problem.
>
Thanks! Removing the header files is a much cleaner solution. I will
remove this patch and use yours.
Irina
prev parent reply other threads:[~2012-09-02 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-28 21:59 [PATCH 03/13] perf tools: drop asm/byteorder.h wrapper Irina Tirdea
2012-08-29 16:19 ` David Ahern
2012-09-02 19:58 ` Irina Tirdea [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=CANg8OWKK7dgc46ddaZddhJGeTT_GWS7Swn2czTsrk+yP65tM1g@mail.gmail.com \
--to=irina.tirdea@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=rostedt@goodmis.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 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).