From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-trace-devel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: [PATCH 0/2] [RFC] several build fixes
Date: Tue, 6 Aug 2019 14:59:48 +0900 [thread overview]
Message-ID: <20190806055950.23842-1-sergey.senozhatsky@gmail.com> (raw)
Hi,
RFC
These patches fix v1.1.1 build on my system.
Sergey Senozhatsky (2):
parse-event: rename filter_arg_boolean arg
makefile: fix python SyntaxError
Makefile | 2 +-
parse-events.h | 2 +-
parse-filter.c | 32 ++++++++++++++++----------------
3 files changed, 18 insertions(+), 18 deletions(-)
--
2.22.0
next reply other threads:[~2019-08-06 5:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 5:59 Sergey Senozhatsky [this message]
2019-08-06 5:59 ` [PATCH 1/2] parse-event: rename filter_arg_boolean arg Sergey Senozhatsky
2019-08-06 5:59 ` [PATCH 2/2] makefile: fix python SyntaxError Sergey Senozhatsky
2019-08-06 13:27 ` [PATCH 0/2] [RFC] several build fixes Steven Rostedt
2019-08-06 13:35 ` Sergey Senozhatsky
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=20190806055950.23842-1-sergey.senozhatsky@gmail.com \
--to=sergey.senozhatsky.work@gmail.com \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@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).