From: Yordan Karadzhov <y.karadz@gmail.com>
To: "Chen, Hongzhan" <hongzhan.chen@intel.com>,
"linux-trace-devel@vger.kernel.org"
<linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH V4 2/3] kernel-shark: Move common APIs and definitions out to avoid duplication
Date: Tue, 11 Jan 2022 10:32:16 +0200 [thread overview]
Message-ID: <1c1072b2-14e6-2735-e065-732cc69a9938@gmail.com> (raw)
In-Reply-To: <MN2PR11MB42853BA4A6B28E23BBADF6DEF2519@MN2PR11MB4285.namprd11.prod.outlook.com>
On 11.01.22 г. 10:03 ч., Chen, Hongzhan wrote:
> I will modify it .Sorry for the inconvenience.
No worries.
cheers,
Y.
next prev parent reply other threads:[~2022-01-11 8:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 4:25 [PATCH V4 1/3] kernel-shark: fix typo in sched_events.h Hongzhan Chen
2022-01-10 4:25 ` [PATCH V4 2/3] kernel-shark: Move common APIs and definitions out to avoid duplication Hongzhan Chen
2022-01-10 13:10 ` Yordan Karadzhov
2022-01-11 8:03 ` Chen, Hongzhan
2022-01-11 8:32 ` Yordan Karadzhov [this message]
2022-01-10 4:25 ` [PATCH V4 3/3] kernel-shark: Add plugin for handling Xenomai cobalt_context_switch Hongzhan Chen
2022-01-10 13:21 ` Yordan Karadzhov
2022-01-10 12:30 ` [PATCH V4 1/3] kernel-shark: fix typo in sched_events.h Yordan Karadzhov
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=1c1072b2-14e6-2735-e065-732cc69a9938@gmail.com \
--to=y.karadz@gmail.com \
--cc=hongzhan.chen@intel.com \
--cc=linux-trace-devel@vger.kernel.org \
/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