From: Steven Rostedt <rostedt@goodmis.org>
To: "Uhanov, Kirill" <kirill.uhanov@intel.com>
Cc: "linux-trace-devel@vger.kernel.org" <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH ]trace-recorder.c
Date: Wed, 4 Sep 2019 06:29:49 -0400 [thread overview]
Message-ID: <20190904062949.44aa1dd4@oasis.local.home> (raw)
In-Reply-To: <E9875C329132824C9E8D827BD6069E125C64C39A@irsmsx110.ger.corp.intel.com>
On Mon, 2 Sep 2019 11:23:18 +0000
"Uhanov, Kirill" <kirill.uhanov@intel.com> wrote:
> Hope is ok if I just add sign-off file.
Hi Kirill,
Could you resend it again starting with "[PATCH]" in the subject, and
not as an attachment. Otherwise your patch doesn't get picked up by
Patchwork and it breaks the flow of adding patches into the git repo.
As I'm traveling, I can't enter your patch into the machine with the
git repo without it being in patchwork. If I was home, I would be able
to do it manually.
Thanks!
-- Steve
prev parent reply other threads:[~2019-09-04 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 11:23 [PATCH ]trace-recorder.c Uhanov, Kirill
2019-09-04 10:29 ` 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=20190904062949.44aa1dd4@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=kirill.uhanov@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;
as well as URLs for NNTP newsgroup(s).