All of lore.kernel.org
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rcojocaru@bitdefender.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Tim Deegan <tim@xen.org>,
	kevin.tian@intel.com, ian.campbell@citrix.com,
	stefano.stabellini@eu.citrix.com,
	Jun Nakajima <jun.nakajima@intel.com>,
	andrew.cooper3@citrix.com, ian.jackson@eu.citrix.com,
	xen-devel@lists.xen.org, Eddie Dong <eddie.dong@intel.com>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH RFC V11 0/5] Basic guest memory introspection support
Date: Tue, 02 Sep 2014 22:13:15 +0300	[thread overview]
Message-ID: <540616CB.7080605@bitdefender.com> (raw)
In-Reply-To: <20140902185350.GA2893@laptop.dumpdata.com>

On 09/02/14 21:53, Konrad Rzeszutek Wilk wrote:
> On Tue, Sep 02, 2014 at 06:37:09PM +0300, Razvan Cojocaru wrote:
>> I apologize, I've sent this as a duplicate V10.
>> Here it is, resent (correctly) as V11. Sorry.
> 
> You also have the RFC part on the patchset. Is that intentional?
> Some maintainers (looks at himself) ignore (well, put it in the
> 'todo pile' to be exact) patches like that until they are
> more mature (non-RFC) and then they will review them.
> 
> I think the RFC part of the patches has been rubbed up as
> the design is pretty baked?

Thanks for the comment, I was actually going to ask about that. I
thought I'd keep the "RFC" in the title until I get Acks for all the
patches, and then switch the prefix to "PATCH", but I'm not sure what
the etiquette is in these cases.

Also, in this particular case I've reworked the 4/5 patch (the page
fault injection patch), so I thought it might be proper to keep the
"RFC" part for the whole series.

I'll switch to "PATCH" for the next series.


Thanks,
Razvan Cojocaru

  reply	other threads:[~2014-09-02 19:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-02 15:37 [PATCH RFC V11 0/5] Basic guest memory introspection support Razvan Cojocaru
2014-09-02 18:53 ` Konrad Rzeszutek Wilk
2014-09-02 19:13   ` Razvan Cojocaru [this message]
2014-09-02 20:15     ` Konrad Rzeszutek Wilk

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=540616CB.7080605@bitdefender.com \
    --to=rcojocaru@bitdefender.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=eddie.dong@intel.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=konrad.wilk@oracle.com \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=tim@xen.org \
    --cc=xen-devel@lists.xen.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 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.