From: Dario Faggioli <dario.faggioli@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
Ian Jackson <ian.jackson@citrix.com>,
Massimo Canonico <mex@di.unipmn.it>,
xen-devel@lists.xen.org
Subject: Re: [PATCH] docs: Make note for the scheduler "cap" option warning about power management effects
Date: Wed, 12 Jun 2013 11:58:59 +0200 [thread overview]
Message-ID: <1371031139.20028.77.camel@Solace> (raw)
In-Reply-To: <1371030255.24512.384.camel@zakaz.uk.xensource.com>
[-- Attachment #1.1: Type: text/plain, Size: 1051 bytes --]
On mer, 2013-06-12 at 10:44 +0100, Ian Campbell wrote:
> On Tue, 2013-06-11 at 13:31 +0100, George Dunlap wrote:
> > Suggested-by: Massimo Canonico <mex@di.unipmn.it>
> > Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
> > CC: Ian Campbell <ian.campbell@citrix.com>
> > CC: Ian Jackson <ian.jackson@citrix.com>
> > CC: Massimo Canonico <mex@di.unipmn.it>
>
> Seems a bit repetitive but Acked + applied (with Dario's reviewed-by
> too)
>
I suppose it is but, given how weird the BIOSes might behave with
respect to this, and looking at how much time it took to track down an
issue that this was causing (compared to what the issue really was!)...
Well, better state it a couple of times than leave _any_ room for people
not noticing it! :-P
Thanks,
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: 198 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:[~2013-06-12 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 12:31 [PATCH] docs: Make note for the scheduler "cap" option warning about power management effects George Dunlap
2013-06-11 15:32 ` Massimo Canonico
2013-06-12 8:48 ` Dario Faggioli
2013-06-12 8:41 ` Dario Faggioli
2013-06-12 9:44 ` Ian Campbell
2013-06-12 9:58 ` Dario Faggioli [this message]
2013-06-12 13:57 ` Konrad Rzeszutek Wilk
2013-06-12 14:59 ` Ian Campbell
2013-06-12 15:01 ` George Dunlap
2013-06-14 18:38 ` Konrad Rzeszutek Wilk
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=1371031139.20028.77.camel@Solace \
--to=dario.faggioli@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@citrix.com \
--cc=mex@di.unipmn.it \
--cc=xen-devel@lists.xen.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).