All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Cc: linux-trace-devel@vger.kernel.org, tz.stoyanov@gmail.com
Subject: Re: [PATCH v4 0/5] Refactor the APIs for tracing options
Date: Fri, 9 Apr 2021 14:26:14 -0400	[thread overview]
Message-ID: <20210409142614.03adf601@gandalf.local.home> (raw)
In-Reply-To: <20210409180423.72497-1-y.karadz@gmail.com>

On Fri,  9 Apr 2021 21:04:18 +0300
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com> wrote:

> Yordan Karadzhov (VMware) (5):
>   libtracefs: Fix issues with tracefs_option_id()
>   libtracefs: Modify the arguments of tracefs_option_is_set()
>   libtracefs: Encapsulate "struct tracefs_options_mask"
>   libtracefs: Option's bit masks to be owned by the instance
>   libtracefs: Rename tracefs_option_is_set()
> 
>  Documentation/libtracefs-option-bits.txt |  10 +--
>  Documentation/libtracefs-option-get.txt  |   7 +-
>  include/tracefs-local.h                  |  12 +++
>  include/tracefs.h                        |  11 +--
>  src/tracefs-instance.c                   |  15 ++++
>  src/tracefs-tools.c                      | 103 +++++++++--------------
>  utest/tracefs-utest.c                    |  12 +--
>  7 files changed, 81 insertions(+), 89 deletions(-)
> 

Bah, I just noticed this patch series after sending out my own.

OK, I'll use this one and see if it covers everything.

Thanks!

-- Steve


WARNING: multiple messages have this Message-ID (diff)
From: Steven Rostedt <rostedt@goodmis.org>
To: "Yordan Karadzhov (VMware)" <y.karadz@gmail.com>
Cc: linux-trace-devel@vger.kernel.org, tz.stoyanov@gmail.com
Subject: Re: [PATCH v4 0/5] Refactor the APIs for tracing options
Date: Fri, 9 Apr 2021 14:26:23 -0400	[thread overview]
Message-ID: <20210409142614.03adf601@gandalf.local.home> (raw)
Message-ID: <20210409182623.Z3Iz98__BH7iZTbAs1MY9wZ3X-Xqw9MDg5uDDqtZieo@z> (raw)
In-Reply-To: <20210409180423.72497-1-y.karadz@gmail.com>

On Fri,  9 Apr 2021 21:04:18 +0300
"Yordan Karadzhov (VMware)" <y.karadz@gmail.com> wrote:

> Yordan Karadzhov (VMware) (5):
>   libtracefs: Fix issues with tracefs_option_id()
>   libtracefs: Modify the arguments of tracefs_option_is_set()
>   libtracefs: Encapsulate "struct tracefs_options_mask"
>   libtracefs: Option's bit masks to be owned by the instance
>   libtracefs: Rename tracefs_option_is_set()
> 
>  Documentation/libtracefs-option-bits.txt |  10 +--
>  Documentation/libtracefs-option-get.txt  |   7 +-
>  include/tracefs-local.h                  |  12 +++
>  include/tracefs.h                        |  11 +--
>  src/tracefs-instance.c                   |  15 ++++
>  src/tracefs-tools.c                      | 103 +++++++++--------------
>  utest/tracefs-utest.c                    |  12 +--
>  7 files changed, 81 insertions(+), 89 deletions(-)
> 

Bah, I just noticed this patch series after sending out my own updates to
the last one.

OK, I'll use this one and see if it covers everything.

Thanks!

-- Steve


  parent reply	other threads:[~2021-04-09 18:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 18:04 [PATCH v4 0/5] Refactor the APIs for tracing options Yordan Karadzhov (VMware)
2021-04-09 18:04 ` [PATCH v4 1/5] libtracefs: Fix issues with tracefs_option_id() Yordan Karadzhov (VMware)
2021-04-09 18:04 ` [PATCH v4 2/5] libtracefs: Modify the arguments of tracefs_option_is_set() Yordan Karadzhov (VMware)
2021-04-09 18:04 ` [PATCH v4 3/5] libtracefs: Encapsulate "struct tracefs_options_mask" Yordan Karadzhov (VMware)
2021-04-09 18:04 ` [PATCH v4 4/5] libtracefs: Option's bit masks to be owned by the instance Yordan Karadzhov (VMware)
2021-04-09 18:40   ` Steven Rostedt
2021-04-09 18:04 ` [PATCH v4 5/5] libtracefs: Rename tracefs_option_is_set() Yordan Karadzhov (VMware)
2021-04-09 18:26 ` Steven Rostedt [this message]
2021-04-09 18:26   ` [PATCH v4 0/5] Refactor the APIs for tracing options 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=20210409142614.03adf601@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=tz.stoyanov@gmail.com \
    --cc=y.karadz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.