From: Steven Rostedt <rostedt@goodmis.org>
To: Yordan Karadzhov <ykaradzhov@vmware.com>
Cc: "linux-trace-devel@vger.kernel.org"
<linux-trace-devel@vger.kernel.org>,
"y.karadz@gmail.com" <y.karadz@gmail.com>
Subject: Re: [PATCH 1/2] kernel-shark: Fix a bug in ksmodel_set_next_bin_edge() part II
Date: Wed, 12 Jun 2019 10:48:15 -0400 [thread overview]
Message-ID: <20190612104815.57ccfb54@gandalf.local.home> (raw)
In-Reply-To: <8451f71f-1078-9d64-5abf-3ed6f36403e1@vmware.com>
On Wed, 12 Jun 2019 14:34:52 +0000
Yordan Karadzhov <ykaradzhov@vmware.com> wrote:
> Hi Steven,
>
> My idea was to make clear that those two patches are strongly connected
> to the patch another patch called:
> kernel-shark: Fix a bug in ksmodel_set_next_bin_edge()
It's best to note the connection in the git change log, and also use a
Fixes: tag.
>
> which was send long time ago.
>
> Should I resend with another subject?
Yes please.
Thanks!
-- Steve
prev parent reply other threads:[~2019-06-12 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-12 14:20 [PATCH 1/2] kernel-shark: Fix a bug in ksmodel_set_next_bin_edge() part II Yordan Karadzhov
2019-06-12 14:20 ` [PATCH 2/2] kernel-shark: Fix a bug in ksmodel_set_next_bin_edge() part III Yordan Karadzhov
2019-06-12 14:28 ` [PATCH 1/2] kernel-shark: Fix a bug in ksmodel_set_next_bin_edge() part II Steven Rostedt
2019-06-12 14:34 ` Yordan Karadzhov
2019-06-12 14:48 ` 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=20190612104815.57ccfb54@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=y.karadz@gmail.com \
--cc=ykaradzhov@vmware.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).