From: Dario Faggioli <dario.faggioli@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel@lists.xenproject.org
Cc: Lars Kurth <lars.kurth@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Anshul Makkar <anshul.makkar@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Meng Xu <mengxu@cis.upenn.edu>, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH 0/3 for 4.8] docs: feature documents for the schedulers
Date: Thu, 13 Oct 2016 13:44:28 +0100 [thread overview]
Message-ID: <1476362668.3314.6.camel@citrix.com> (raw)
In-Reply-To: <b42876bb-6428-888b-9f25-2f55f413eb5e@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1214 bytes --]
On Thu, 2016-10-13 at 12:28 +0100, Andrew Cooper wrote:
> On 13/10/16 12:01, Dario Faggioli wrote:
> > "Just" as per the subject, I wrote feature documents for (almost)
> > all our
> > schedulers. No big deal, I'd say, apart from the fact that I'm
> > declaring
> > Credit2 **Supperted**, instead of experimental.
>
> Supperted? That's like supported right? ;p
>
Nah, 'supperted' is the new 'supported', didn't you know? :-P
> It is fine for you to propose that a feature should be upgraded to
> supported, and this is probably the best way to formally do so.
>
> However, final agreement of a feature becoming supported should
> include
> input from the security team. (At the end of the day, it is us with
> extra work if the feature isn't up to scratch.)
>
Ok, so, if that's the case, what's the process: resend (this patch) --
or some other kind of formal request-- with security@xenproject.org
Cc-ed?
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-13 12:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 11:01 [PATCH 0/3 for 4.8] docs: feature documents for the schedulers Dario Faggioli
2016-10-13 11:02 ` [PATCH 1/3] docs: Credit1 feature document Dario Faggioli
2016-10-13 11:43 ` Wei Liu
2016-10-13 11:47 ` Andrew Cooper
2016-10-13 13:26 ` Dario Faggioli
2016-10-13 11:03 ` [PATCH 2/3] docs: Credit2 " Dario Faggioli
2016-10-13 11:04 ` [PATCH 3/3] docs: RTDS " Dario Faggioli
2016-10-13 11:28 ` [PATCH 0/3 for 4.8] docs: feature documents for the schedulers Andrew Cooper
2016-10-13 11:36 ` George Dunlap
2016-10-13 12:44 ` Dario Faggioli [this message]
2016-10-13 12:46 ` Wei Liu
2016-10-14 8:55 ` Dario Faggioli
2016-10-13 18:13 ` Stefano Stabellini
2016-10-13 20:10 ` Konrad Rzeszutek Wilk
2016-10-13 21:06 ` Stefano Stabellini
2016-10-14 0:31 ` Andrew Cooper
2016-10-14 0:58 ` Stefano Stabellini
2016-10-14 6:36 ` Jan Beulich
2016-10-14 9:59 ` George Dunlap
2016-10-14 10:11 ` Jan Beulich
2016-10-14 20:03 ` Stefano Stabellini
2016-10-14 18:53 ` Stefano Stabellini
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=1476362668.3314.6.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=anshul.makkar@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=lars.kurth@citrix.com \
--cc=mengxu@cis.upenn.edu \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.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.