All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: tu bo <tubo@linux.vnet.ibm.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	mreitz@redhat.com, mimu@linux.vnet.ibm.com,
	qemu-devel@nongnu.org, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH RFC v9 0/7] Update tests/qemu-iotests failing cases for the s390 platform
Date: Thu, 28 May 2015 12:01:24 +0200	[thread overview]
Message-ID: <20150528120124.036c4178@thh440s> (raw)
In-Reply-To: <556699C5.2030306@linux.vnet.ibm.com>


 Hi Tu Bo!

On Thu, 28 May 2015 12:29:57 +0800
tu bo <tubo@linux.vnet.ibm.com> wrote:

> Hi Kevin:
> 
> On 05/26/2015 07:55 PM, Kevin Wolf wrote:
...
> > Is this still an RFC series, as the subject indicates, or is it meant
> > for inclusion?
> This is my first task for qemu which I took over from Xiao Guang Chen, 
> and I'm not sure if I understand it well.  Does 'RFC' mean 'Reference 
> for Candidate'?  please correct me if I'm wrong.  If other actions I 
> need to take, please let me know.

RFC means "Request for comments". You put it into a patch title if you
want to get some comments about your patches, but don't consider them
good enough for inclusion yet. See also the patch submission guideline
for details: http://qemu-project.org/Contribute/SubmitAPatch

> Anyway,  this patch series is final version.  thanks

I that case the title should normally not include "RFC" anymore.

 Regards,
  Thomas

  reply	other threads:[~2015-05-28 10:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25  3:30 [Qemu-devel] [PATCH RFC v9 0/7] Update tests/qemu-iotests failing cases for the s390 platform Bo Tu
2015-05-25  3:30 ` [Qemu-devel] [PATCH RFC v9 1/7] qemu-iotests: qemu machine type support Bo Tu
2015-05-25  3:30 ` [Qemu-devel] [PATCH RFC v9 2/7] qemu-iotests: run qemu with -nodefaults and fix 067, 071, 081 and 087 Bo Tu
2015-05-25  3:30 ` [Qemu-devel] [PATCH RFC v9 3/7] qemu-iotests: s390x: fix test 041 Bo Tu
2015-05-25  3:30 ` [Qemu-devel] [PATCH RFC v9 4/7] qemu-iotests: s390x: fix test 055 Bo Tu
2015-05-25  3:30 ` [Qemu-devel] [PATCH RFC v9 5/7] qemu-iotests: s390x: fix test 049 Bo Tu
2015-05-25  3:30 ` [Qemu-devel] [PATCH RFC v9 6/7] qemu-iotests: s390x: fix test 051 Bo Tu
2015-05-25  3:30 ` [Qemu-devel] [PATCH RFC v9 7/7] qemu-iotests: s390x: fix test 130 Bo Tu
2015-05-26 11:55 ` [Qemu-devel] [PATCH RFC v9 0/7] Update tests/qemu-iotests failing cases for the s390 platform Kevin Wolf
2015-05-28  4:29   ` tu bo
2015-05-28 10:01     ` Thomas Huth [this message]
2015-05-28 10:27       ` tu bo
  -- strict thread matches above, loose matches on Subject: below --
2015-05-22  1:26 Bo Tu

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=20150528120124.036c4178@thh440s \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mimu@linux.vnet.ibm.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=tubo@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.