From: Steven Rostedt <rostedt@goodmis.org>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH] trace-cmd: Report unknown VMX exit reasons with code
Date: Fri, 4 Oct 2013 10:50:34 -0400 [thread overview]
Message-ID: <20131004105034.5d8e8569@gandalf.local.home> (raw)
In-Reply-To: <524EC54D.5060503@web.de>
On Fri, 04 Oct 2013 15:40:29 +0200
Jan Kiszka <jan.kiszka@web.de> wrote:
> Ping. While my other patch of that time was merged, this one didn't make
> it yet. Any open issues?
Hmm, no. Not sure how I missed this one. Probably because it didn't
have the 2/2 patch format and I thought there was only one patch?
I'll queue it up.
Thanks!
-- Steve
prev parent reply other threads:[~2013-10-04 14:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-11 7:59 [PATCH] trace-cmd: Report unknown VMX exit reasons with code Jan Kiszka
2013-10-04 13:40 ` Jan Kiszka
2013-10-04 14:50 ` 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=20131004105034.5d8e8569@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=jan.kiszka@web.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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).