mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zamir SUN <sztsian@gmail.com>
To: rostedt@goodmis.org
Cc: johannes.berg@intel.com, johannes@sipsolutions.net,
	linux-kernel@vger.kernel.org, zsun@redhat.com
Subject: Re: [PATCH 0/2] trace-cmd: Improves python plugin support
Date: Tue, 6 Feb 2018 20:31:54 +0800	[thread overview]
Message-ID: <18dbee92-3f25-781f-9beb-7bef9d6c12d9@gmail.com> (raw)
In-Reply-To: <20180204032014.6962-1-sztsian@gmail.com>

Hi Steve,

Do you have any thoughts for this?

Thanks.

On 02/04/2018 11:20 AM, sztsian@gmail.com wrote:
> From: Zamir SUN (Red Hat) <sztsian@gmail.com>
> 
> This is a set of patch to improve trace-cmd python plugin support.
> 
> Patch 1 fixes the detection for swig. With this patch, python-plugin can
> be built successfully.
> 
> Patch 2 improves the detection for python ldflags. With this patch,
> ldflags can be detected with python3 in the future.
> 
> Zamir SUN (2):
>   trace-cmd: Fix the detection for swig
>   trace-cmd: Change the way of getting python ldflags.
> 
>  Makefile | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 

-- 
Zamir SUN
Fedora user
GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E

  parent reply	other threads:[~2018-02-06 12:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04  3:20 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
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 ` Zamir SUN [this message]
2018-02-06 14:14   ` [PATCH 0/2] trace-cmd: Improves python plugin support 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=18dbee92-3f25-781f-9beb-7bef9d6c12d9@gmail.com \
    --to=sztsian@gmail.com \
    --cc=johannes.berg@intel.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --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
Powered by JetHome