From: Dario Faggioli <dario.faggioli@citrix.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: xen-devel@lists.xenproject.org,
Ian Campbell <ian.campbell@citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <ian.jackson@eu.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:43:02 +0200 [thread overview]
Message-ID: <1436204582.10763.47.camel@citrix.com> (raw)
In-Reply-To: <559AAB37.8010003@eu.citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1948 bytes --]
On Mon, 2015-07-06 at 17:22 +0100, George Dunlap wrote:
> On 07/06/2015 05:17 PM, Dario Faggioli wrote:
> > On Mon, 2015-07-06 at 16:40 +0100, George Dunlap wrote:
> >> On 07/06/2015 04:30 PM, Dario Faggioli wrote:
> >>> only the interface is left in place, for backward
> >>> compile-time compatibility, but every attempt to
> >>> use it would throw an error.
> >>>
> >>> Signed-off-by: Dario Faggioli <dario.faggioli@citrix.com>
> >>> Reviewed-by: George Dunlap <george.dunlap@eu.citrix.com>
> >>
> >> This probably should have been dropped...
> >>
> >>> Chenges from v2:
> >>> - introduce and use ERROR_FEATURE_REMOVED, as requested
> >>> during review;
> >>> - mark the SEDF only parameter as deprecated in libxl_types.idl,
> >>> as requested during review.
> >>
> >> ...given these. One question:
> >>
> > Really? I'm basically only adding commentary, not changing (or adding,
> > or removing) a single line of code... I mean, the deprecation was
> > de-facto there already, since v1, it just was not stated explicitly
> > anywhere in that particular file.
> >
> > That's why I didn't think a something like adding this comment would
> > call for removal of the tag.
> >
> > Anyway, sorry for this. :-)
>
> Not a big deal of course, and as it happens I wouldn't have minded if
> the patch went in as it is.
>
Sure! :-) I also was also just explaining my reasoning, rather than
complaining.
> But what if I hadn't liked the name of the
> error code? It looks like I approve of it, which might sway some
> maintainer's view, when in fact I haven't expressed an opinion.
>
Indeed, I see it know.
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:43 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
2015-07-06 17:43 ` Dario Faggioli [this message]
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=1436204582.10763.47.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.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).