From: Wei Liu <wei.liu2@citrix.com>
To: Dario Faggioli <dario.faggioli@citrix.com>
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>,
Andrew Cooper <andrew.cooper3@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>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH 0/3 for 4.8] docs: feature documents for the schedulers
Date: Thu, 13 Oct 2016 13:46:30 +0100 [thread overview]
Message-ID: <20161013124629.GI3687@citrix.com> (raw)
In-Reply-To: <1476362668.3314.6.camel@citrix.com>
On Thu, Oct 13, 2016 at 01:44:28PM +0100, Dario Faggioli wrote:
> 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?
>
If you want these to be applied more quickly the best thing to do is to
leave the status experimental and later send another patch with
security@ CC'ed to change the status.
Wei.
> 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)
_______________________________________________
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:46 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
2016-10-13 12:46 ` Wei Liu [this message]
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=20161013124629.GI3687@citrix.com \
--to=wei.liu2@citrix.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=anshul.makkar@citrix.com \
--cc=dario.faggioli@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=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 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).