From: Steven Rostedt <rostedt@goodmis.org>
To: Yordan Karadzhov <y.karadz@gmail.com>
Cc: Hongzhan Chen <hongzhan.chen@intel.com>,
linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v2 0/2]kernel-shark:add new plugin for xenomai cobalt_switch_context events
Date: Thu, 6 Jan 2022 13:32:04 -0500 [thread overview]
Message-ID: <20220106133204.35d71b6b@gandalf.local.home> (raw)
In-Reply-To: <5de4819d-2f49-86c0-900d-a4aa585b67ec@gmail.com>
On Thu, 6 Jan 2022 19:32:56 +0200
Yordan Karadzhov <y.karadz@gmail.com> wrote:
> Hi Steven,
> Happy New Year!
Happy New Year to you too Yordan!
>
> I already replayed, asking for some minor corrections.
> https://lore.kernel.org/all/bb1741d5-600a-82a9-d8bc-91222400e129@gmail.com/
> I think the plugin is almost ready.
Strange, I didn't receive it. I wonder if I got booted from the email lists
because I had my mail server offline for too long (/me goes check).
>
> BTW have you finished the renovation of your office? If yes, I will send you a review for your trace-cruncher patch.
>
Yes, I just finished. Now I'm trying to catch up on everything and also
work on some things that I may not be able to work on when I start working
again.
Cheers,
-- Steve
prev parent reply other threads:[~2022-01-06 18:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 6:40 [PATCH v2 0/2]kernel-shark:add new plugin for xenomai cobalt_switch_context events Hongzhan Chen
2021-12-22 6:40 ` [PATCH v2 1/2] kernel-shark: Move common APIs and definitions out to avoid duplication Hongzhan Chen
2022-01-05 11:34 ` Yordan Karadzhov
2021-12-22 6:40 ` [PATCH v2 2/2] kernel-shark: Add plugin for handling Xenomai cobalt_context_switch Hongzhan Chen
2022-01-05 11:32 ` [PATCH v2 0/2]kernel-shark:add new plugin for xenomai cobalt_switch_context events Yordan Karadzhov
2022-01-06 17:18 ` Steven Rostedt
2022-01-06 17:32 ` Yordan Karadzhov
2022-01-06 18:32 ` Steven Rostedt [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=20220106133204.35d71b6b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=hongzhan.chen@intel.com \
--cc=linux-trace-devel@vger.kernel.org \
--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.