From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH v3 1/7] libxl: get rid of the SEDF scheduler
Date: Mon, 6 Jul 2015 19:44:14 +0200 [thread overview]
Message-ID: <1436204654.10763.49.camel@citrix.com> (raw)
In-Reply-To: <21914.44075.56339.297524@mariner.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1138 bytes --]
On Mon, 2015-07-06 at 17:26 +0100, Ian Jackson wrote:
> George Dunlap writes ("Re: [Xen-devel] [PATCH v3 1/7] libxl: get rid of the SEDF scheduler"):
> > On 07/06/2015 05:17 PM, Dario Faggioli wrote:
> > I probably wouldn't even have bothered saying anything if I hadn't
> > already been replying to the e-mail because of the line below. :-)
>
> Also, while public-facing API comments are only comments (only
> documentation), they are quite important.
>
> A change like this:
>
> > >>> - mark the SEDF only parameter as deprecated in libxl_types.idl,
> > >>> as requested during review.
>
> warrants dropping an acked/reviewed-by (unless it was requested or
> suggested by the reviewer).
>
Right, makes sense, and I see it now. Thanks. :-)
So, while you're here, should I send v4 with the 'budget' field moved
up?
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: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-07-06 17:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 15:30 [PATCH v3 0/7] get rid of the SEDF Dario Faggioli
2015-07-06 15:30 ` [PATCH v3 1/7] libxl: get rid of the SEDF scheduler Dario Faggioli
2015-07-06 15:40 ` George Dunlap
2015-07-06 16:17 ` Dario Faggioli
2015-07-06 16:22 ` George Dunlap
2015-07-06 16:26 ` Ian Jackson
2015-07-06 17:44 ` Dario Faggioli [this message]
2015-07-06 17:43 ` Dario Faggioli
2015-07-07 13:48 ` Ian Campbell
2015-07-07 14:15 ` Ian Campbell
2015-07-07 14:19 ` George Dunlap
2015-07-07 14:22 ` Ian Campbell
2015-07-07 15:50 ` Dario Faggioli
2015-07-07 15:10 ` R: " Dario Faggioli
2015-07-06 15:30 ` [PATCH v3 2/7] tools: python: get rid of the SEDF scheduler bindings Dario Faggioli
2015-07-06 15:30 ` [PATCH v3 3/7] libxc: get rid of the SEDF scheduler Dario Faggioli
2015-07-06 15:31 ` [PATCH v3 4/7] xen: " Dario Faggioli
2015-07-06 15:31 ` [PATCH v3 5/7] xen: kill sched_sedf.c Dario Faggioli
2015-07-06 15:31 ` [PATCH v3 6/7] xl: get rid of the SEDF scheduler Dario Faggioli
2015-07-06 15:31 ` [PATCH v3 7/7] docs: " 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=1436204654.10763.49.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--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).