All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Tim Deegan <tim@xen.org>
Cc: Kevin Tian <kevin.tian@intel.com>, Keir Fraser <keir@xen.org>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Steven Maresca <steve@zentific.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Tamas Lengyel <tamas.lengyel@zentific.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>,
	Eddie Dong <eddie.dong@intel.com>,
	Andres Lagar Cavilla <andres@lagarcavilla.org>,
	Jan Beulich <jbeulich@suse.com>,
	"rshriram@cs.ubc.ca" <rshriram@cs.ubc.ca>,
	"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
	Daniel De Graaf <dgdegra@tycho.nsa.gov>,
	"yanghy@cn.fujitsu.com" <yanghy@cn.fujitsu.com>,
	Razvan Cojocaru <rcojocaru@bitdefender.com>
Subject: Re: [PATCH V8 00/12] xen: Clean-up of mem_event subsystem
Date: Tue, 14 Apr 2015 12:31:51 +0100	[thread overview]
Message-ID: <1429011111.15516.37.camel@citrix.com> (raw)
In-Reply-To: <20150409113020.GC17025@deinos.phlegethon.org>

On Thu, 2015-04-09 at 12:30 +0100, Tim Deegan wrote:
> > What's the policy on reusing DOMCTL numbers? I see
> > XEN_DOMCTL_arm_configure_domain
> > has been retired in the conflicting patch. Should I just reuse it's number
> > for monitor_op? For the most part domctl numbers seem to be continuous but
> > there are holes (30-32) so I'm not sure.
> 
> I'm not sure either.  I'd be inlclined to leave a hole here, to avoid
> any accidental confusion with the recently-removed op, but other
> maintainers may disagree. :)

I also think we should leave a hole. And perhaps we should have left a
"previous used as" type comment when removing arm_configure_domain,
sorry for not thinking of that at the time...

Ian.

      reply	other threads:[~2015-04-14 11:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 21:06 [PATCH V8 00/12] xen: Clean-up of mem_event subsystem Tamas K Lengyel
2015-03-26 21:06 ` [PATCH V8 01/12] xen/mem_event: Cleanup of mem_event structures Tamas K Lengyel
2015-03-26 21:06 ` [PATCH V8 02/12] xen/mem_event: Cleanup mem_event names in rings, functions and domctls Tamas K Lengyel
2015-03-26 21:06 ` [PATCH V8 03/12] xen/mem_paging: Convert mem_event_op to mem_paging_op and cleanup Tamas K Lengyel
2015-03-26 21:06 ` [PATCH V8 04/12] xen: Rename mem_event to vm_event Tamas K Lengyel
2015-03-26 21:06 ` [PATCH V8 05/12] tools/tests: Clean-up tools/tests/xen-access Tamas K Lengyel
2015-03-26 21:06 ` [PATCH V8 06/12] x86/hvm: factor out and rename vm_event related functions Tamas K Lengyel
2015-03-26 21:06 ` [PATCH V8 07/12] xen: Introduce monitor_op domctl Tamas K Lengyel
2015-03-27 10:20   ` Jan Beulich
2015-03-26 21:07 ` [PATCH V8 08/12] xen/vm_event: Deprecate VM_EVENT_FLAG_DUMMY flag Tamas K Lengyel
2015-03-26 21:07 ` [PATCH V8 09/12] xen/vm_event: Decouple vm_event and mem_access Tamas K Lengyel
2015-03-26 21:07 ` [PATCH V8 10/12] xen/vm_event: Relocate memop checks Tamas K Lengyel
2015-03-26 21:07 ` [PATCH V8 11/12] xen/xsm: Split vm_event_op into three separate labels Tamas K Lengyel
2015-03-26 21:07 ` [PATCH V8 12/12] xen/vm_event: Add RESUME option to vm_event_op domctl Tamas K Lengyel
2015-04-09 11:03 ` [PATCH V8 00/12] xen: Clean-up of mem_event subsystem Tim Deegan
2015-04-09 11:07   ` Tamas Lengyel
2015-04-09 11:15     ` Tamas Lengyel
2015-04-09 11:21       ` Andrew Cooper
2015-04-09 11:30       ` Tim Deegan
2015-04-14 11:31         ` Ian Campbell [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=1429011111.15516.37.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=andres@lagarcavilla.org \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=eddie.dong@intel.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=kevin.tian@intel.com \
    --cc=rcojocaru@bitdefender.com \
    --cc=rshriram@cs.ubc.ca \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=steve@zentific.com \
    --cc=tamas.lengyel@zentific.com \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=yanghy@cn.fujitsu.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.