From: Will Schmidt <will_schmidt@vnet.ibm.com>
To: rostedt@goodmis.org
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
mingo@redhat.com, Anton Blanchard <anton@samba.org>
Subject: Re: hypervisor call tracepoints hcall_stats touchup.
Date: Mon, 30 Nov 2009 09:17:52 -0600 [thread overview]
Message-ID: <1259594272.16349.393.camel@lexx> (raw)
In-Reply-To: <1259183974.21397.73.camel@gandalf.stny.rr.com>
On Wed, 2009-11-25 at 16:19 -0500, Steven Rostedt wrote:
> On Wed, 2009-11-25 at 10:12 -0600, Will Schmidt wrote:
>
> > Tested-by: Will Schmidt <will_schmidt@vnet.ibm.com>
> > Signed-off-by: Will Schmidt <will_schmidt@vnet.ibm.com>
>
> Isn't it assumed that the one that made the patch also tested it? Well I
> would hope that is the norm.
I like to make that assumption, but wanted to be clear on the point for
anyone with doubts. :-)
>
> -- Steve
>
>
next prev parent reply other threads:[~2009-11-30 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 16:12 hypervisor call tracepoints hcall_stats touchup Will Schmidt
2009-11-25 21:19 ` Steven Rostedt
2009-11-30 15:17 ` Will Schmidt [this message]
2009-11-26 3:28 ` Anton Blanchard
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=1259594272.16349.393.camel@lexx \
--to=will_schmidt@vnet.ibm.com \
--cc=anton@samba.org \
--cc=fweisbec@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.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