All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars Kurth <lars.kurth@citrix.com>
To: Rich Persaud <persaur@gmail.com>, Jan Beulich <jbeulich@suse.com>
Cc: "Daniel P. Smith" <dpsmith@apertussolutions.com>,
	Doug Goldstein <cardoe@cardoe.com>,
	Julien Grall <julien.grall@arm.com>,
	"anastassios.nanos@onapp.com" <anastassios.nanos@onapp.com>,
	Matt Spencer <Matt.Spencer@arm.com>,
	"edgar.iglesias@xilinx.com" <edgar.iglesias@xilinx.com>,
	John Ji <john.ji@intel.com>,
	"robin.randhawa@arm.com" <robin.randhawa@arm.com>,
	"daniel.kiper@oracle.com" <daniel.kiper@oracle.com>,
	"mirela.simonovic@aggios.com" <mirela.simonovic@aggios.com>,
	xen-devel <xen-devel@lists.xenproject.org>,
	Rian Quinn <rianquinn@gmail.com>, Juergen Gross <jgross@suse.com>,
	Tamas K Lengyel <tamas.k.lengyel@gmail.com>,
	Christopher Clark <christopher.w.clark@gmail.com>,
	Paul Durrant <Paul.Durrant@citrix.com>,
	Ian Jackson <Ian.Jackson@citrix.com>,
	"vfachin@de.adit-jv.com" <vfachin@de.adit-jv.com>,
	"intel-xen@intel.com" <intel-xen@intel.com>,
	Jarvis Roach <Jarvis.Roach@dornerworks.com>,
	Artem Mygaiev <Artem_Mygaiev@epam.com>,
	Sergey Dyasli <sergey.dyasli@citrix.com>,
	Brian Woods <brian.woods@amd.com>,
	Jeff Kubascik <Jeff.Kubascik@dornerworks.com>,
	Janakarajan Natarajan <jnataraj@amd.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Stewart Hildebrand <Stewart.Hildebrand@dornerworks.com>,
	Volodymyr Babchuk <volodymyr_babchuk@epam.com>,
	Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC
Date: Thu, 5 Sep 2019 07:49:39 +0000	[thread overview]
Message-ID: <FA118783-4079-460A-95F8-B628F3320637@citrix.com> (raw)
In-Reply-To: <11D8BF8A-BF9E-4610-8A80-8698B705AFAB@gmail.com>



On 05/09/2019, 08:41, "Rich Persaud" <persaur@gmail.com> wrote:

    > On Sep 5, 2019, at 03:19, Jan Beulich <jbeulich@suse.com> wrote:
    > 
    > Forgive me asking, but why is this put up as an agenda item here?
    > IMO this is the kind of thing where you would send a proposal and
    > request feedback by email first, and put it up as an agenda item
    > here only if it got stalled there. (Apologies if I've overlooked
    > such a stalled thread.)
    
    If Xen community call topics are limited to escalations of xen-devel threads, then a new thread can be created for this topic. Xen community calls have also provided real-time, interactive feedback on candidate proposals, along with guidance on areas which need documentation before a formal proposal is made to xen-devel.   Such agenda items are typically covered after all series and priority topics have been addressed.
    
I don't mind having items such these on the agenda and to be fair have added similar items onto the agenda in the past.
Clearly, they are forward looking [like an RFC], for which reason I tend to add them to the end of an agenda if there is a busy schedule

Personally, on this specific item, it is not really clear what the questions are.  In other words: is this about UUIDS/domain ids only, or is there something else. 

Lars

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-09-05  7:50 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04 14:05 [Xen-devel] [ANNOUNCE] Call for agenda items for September 5th Community Call @ 15:00 UTC Lars Kurth
2019-09-05  2:32 ` Rich Persaud
2019-09-05  7:19   ` Jan Beulich
2019-09-05  7:41     ` Rich Persaud
2019-09-05  7:49       ` Lars Kurth [this message]
2019-09-05  8:14         ` Andrew Cooper
2019-09-05  8:33           ` Juergen Gross
2019-09-05  8:36             ` Lars Kurth
2019-09-05 14:48               ` Rich Persaud
2019-09-05 16:12                 ` Lars Kurth
2019-09-05 16:16                   ` Rich Persaud
2019-09-05  7:50       ` Jan Beulich
2019-09-05  8:00         ` Lars Kurth
2019-09-05  8:06           ` Juergen Gross
2019-09-05  8:19           ` Andrew Cooper
2019-09-05  8:29             ` Steven Haigh
2019-09-05  7:54       ` Juergen Gross

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=FA118783-4079-460A-95F8-B628F3320637@citrix.com \
    --to=lars.kurth@citrix.com \
    --cc=Artem_Mygaiev@epam.com \
    --cc=Ian.Jackson@citrix.com \
    --cc=Jarvis.Roach@dornerworks.com \
    --cc=Jeff.Kubascik@dornerworks.com \
    --cc=Matt.Spencer@arm.com \
    --cc=Paul.Durrant@citrix.com \
    --cc=Stewart.Hildebrand@dornerworks.com \
    --cc=anastassios.nanos@onapp.com \
    --cc=brian.woods@amd.com \
    --cc=cardoe@cardoe.com \
    --cc=christopher.w.clark@gmail.com \
    --cc=daniel.kiper@oracle.com \
    --cc=dpsmith@apertussolutions.com \
    --cc=edgar.iglesias@xilinx.com \
    --cc=intel-xen@intel.com \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=jnataraj@amd.com \
    --cc=john.ji@intel.com \
    --cc=julien.grall@arm.com \
    --cc=mirela.simonovic@aggios.com \
    --cc=persaur@gmail.com \
    --cc=rianquinn@gmail.com \
    --cc=robin.randhawa@arm.com \
    --cc=roger.pau@citrix.com \
    --cc=sergey.dyasli@citrix.com \
    --cc=sstabellini@kernel.org \
    --cc=tamas.k.lengyel@gmail.com \
    --cc=vfachin@de.adit-jv.com \
    --cc=volodymyr_babchuk@epam.com \
    --cc=xen-devel@lists.xenproject.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.