qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Wainer dos Santos Moschetta <wainersm@redhat.com>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, rth@twiddle.net, ehabkost@redhat.com,
	crosa@redhat.com, ccarrara@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] target/i386: Fixes to the check missing features routine
Date: Tue, 11 Dec 2018 13:58:50 -0600	[thread overview]
Message-ID: <e4fcb8eb-16b8-6d2d-b135-b539b7c871cf@redhat.com> (raw)
In-Reply-To: <b9be5998-8914-fce5-bcb7-8ff8780d9dcc@redhat.com>

On 12/11/18 1:47 PM, Wainer dos Santos Moschetta wrote:

> 
> Yes, it helped a lot, thanks. And I apologize for my mistake, I'm gonna 
> send a v3 fixing it.

You may want to wait a day or so for any other comments on v2, to 
minimize the resend churn. A maintainer can fix up tags, particularly 
when they are aware it is from a newer contributor still learning how 
things work.

> 
> Another doubt that I have: is it advisable to CC everyone that reviewed 
> (with or without R-by) the previous version of my patch?

CC'ing previous reviewers is generally a reasonable idea, since they are 
then more likely to double-check that the things they pointed out in the 
first version are indeed fixed in the respin (and since without the cc, 
it's a lot easier to miss that a respin is even available on-list for 
followup review, thanks to the list traffic volume).  You might not get 
a reply from everyone cc'd, but that's not fatal to acceptance of the patch.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

  reply	other threads:[~2018-12-11 19:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 16:28 [Qemu-devel] [PATCH v2] target/i386: Fixes to the check missing features routine Wainer dos Santos Moschetta
2018-12-11 17:15 ` Eric Blake
2018-12-11 19:47   ` Wainer dos Santos Moschetta
2018-12-11 19:58     ` Eric Blake [this message]
2018-12-12  1:32 ` Eduardo Habkost

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=e4fcb8eb-16b8-6d2d-b135-b539b7c871cf@redhat.com \
    --to=eblake@redhat.com \
    --cc=ccarrara@redhat.com \
    --cc=crosa@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=wainersm@redhat.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).