From: Vladislav Valtchev <vladislav.valtchev@gmail.com>
To: Zamir SUN <sztsian@gmail.com>, Steven Rostedt <rostedt@goodmis.org>
Cc: johannes.berg@intel.com, johannes@sipsolutions.net,
linux-kernel@vger.kernel.org, zsun@redhat.com
Subject: Re: [PATCH 1/2] trace-cmd: Fix the detection for swig
Date: Thu, 08 Feb 2018 16:04:17 +0200 [thread overview]
Message-ID: <1518098657.2670.3.camel@gmail.com> (raw)
In-Reply-To: <a1c2c3f6-8d69-227d-51d4-1c40c53e0645@gmail.com>
On Thu, 2018-02-08 at 20:05 +0800, Zamir SUN wrote:
>
> Hi Vladislav,
>
> Thanks for the URL. I tried to build from your make8 branch, it works
> fine. I must made some copy-paste mistake yesterday.
>
> Sorry for the noise.
>
> Thanks.
No problem, Zamir.
I'm happy that it works.
The series has been merged in the master branch by Steven now.
Anyway, I think your patch 2/2 is still necessary: thanks for it!
Vlad
--
Vladislav Valtchev
VMware Open Source Technology Center
next prev parent reply other threads:[~2018-02-08 14:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 3:20 [PATCH 0/2] trace-cmd: Improves python plugin support sztsian
2018-02-04 3:20 ` [PATCH 1/2] trace-cmd: Fix the detection for swig sztsian
2018-02-06 23:18 ` Steven Rostedt
2018-02-07 14:01 ` Zamir SUN
2018-02-07 14:40 ` Steven Rostedt
2018-02-07 15:09 ` Zamir SUN
2018-02-07 17:25 ` Vladislav Valtchev
2018-02-08 12:05 ` Zamir SUN
2018-02-08 14:04 ` Vladislav Valtchev [this message]
2018-02-04 3:20 ` [PATCH 2/2] trace-cmd: Change the way of getting python ldflags sztsian
2018-02-08 23:54 ` Steven Rostedt
2018-03-22 23:13 ` Steven Rostedt
2018-03-23 12:19 ` Zamir SUN
2018-02-06 12:31 ` [PATCH 0/2] trace-cmd: Improves python plugin support Zamir SUN
2018-02-06 14:14 ` Steven Rostedt
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=1518098657.2670.3.camel@gmail.com \
--to=vladislav.valtchev@gmail.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sztsian@gmail.com \
--cc=zsun@redhat.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).