From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@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>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Anshul Makkar <anshul.makkar@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
security@xenproject.org, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH] features: declare the Credit2 scheduler as Supported.
Date: Thu, 27 Oct 2016 17:21:51 +0200 [thread overview]
Message-ID: <1477581711.24942.9.camel@citrix.com> (raw)
In-Reply-To: <6ff90896-8434-d970-283a-711fb77f0174@citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1268 bytes --]
On Thu, 2016-10-27 at 16:01 +0100, George Dunlap wrote:
> On 25/10/16 09:18, Dario Faggioli wrote:
> > All this being said, what's the next step? Is there anything more I
> > should do, here in this thread? Should we wait for other people to
> > weigh in? Should I resend this patch, with a non empty commit
> > message?
> > Containing what, a summary of this?
>
> Well I think that in the absence of official rules, we have to make
> things up as we go along.
>
Fine with me. :-)
> I think to get this enabled now requires someone to send a patch with
> the justification (both from a support/reliability standpoint and
> from a
> security standpoint) in the commit message. If we get a REST
> Maintainer's Ack and no objections, then it should go in (subject to
> the
> release coodinator, of course).
>
Ok.
> Do you want to send such a patch, or would you prefer it if I tried
> to
> write something up?
>
I'd like to give it a try myself.
Thanks and 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-27 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-14 10:17 [PATCH] features: declare the Credit2 scheduler as Supported Dario Faggioli
2016-10-14 10:25 ` Jan Beulich
2016-10-14 10:42 ` George Dunlap
2016-10-25 8:18 ` Dario Faggioli
2016-10-27 15:01 ` George Dunlap
2016-10-27 15:21 ` Dario Faggioli [this message]
2016-11-02 10:33 ` Dario Faggioli
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=1477581711.24942.9.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=george.dunlap@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=lars.kurth@citrix.com \
--cc=security@xenproject.org \
--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 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).