From: Dario Faggioli <dario.faggioli@citrix.com>
To: Xen-devel <xen-devel@lists.xenproject.org>
Cc: Lars Kurth <lars.kurth.xen@gmail.com>,
Doug Goldstein <cardoe@cardoe.com>
Subject: Kconfig docs [was: Re: Xen 4.7 Test Day Instructions for RC2+ : Call to action for people who added new features / functionality to Xen 4.7]
Date: Tue, 10 May 2016 09:50:03 +0200 [thread overview]
Message-ID: <1462866603.4858.17.camel@citrix.com> (raw)
In-Reply-To: <03a11ad2-df72-51d6-9214-2a88c3ecd355@cardoe.com>
[-- Attachment #1.1: Type: text/plain, Size: 1399 bytes --]
[trimming the Cc list]
On Mon, 2016-05-09 at 21:59 -0500, Doug Goldstein wrote:
> On 5/9/16 10:28 AM, Lars Kurth wrote:
> >
> > - Doug: are there any docs / tests for KCONFIG you want to push
> Not at this time. Unless someone has an idea for what they'd like to
>
This is not specifically related to test-day/test-instructions, but as
far as I can tell:
1) there's no wiki page saying that we have Kconfig and how to use it,
2) we haven't blogged about it.
I'd say we should do both, but I guess 2 depends on how much we really
want this possibility of changing the default configuration to be
advertised. As I think the answer is "not much", we may better don't
blog.
But at least 1, I think it should be there.
As a matter of fact, I still haven't given explicitly using Kconfig on
Xen a try yet (despite wanting to), so I'm not sure about the
content... But just something simple stating that it's there, what it
covers (Xen only vs. Xen+tools, etc), how to achieve what's been the
default so far, how to achieve something slightly different...
something like this.
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: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-10 7:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-05 17:08 Xen 4.7 Test Day Instructions for RC2+ : Call to action for people who added new features / functionality to Xen 4.7 Lars Kurth
2016-05-09 15:28 ` Lars Kurth
2016-05-09 16:03 ` George Dunlap
2016-05-09 16:55 ` Lars Kurth
2016-05-10 2:18 ` Dario Faggioli
2016-05-10 4:02 ` Juergen Gross
2016-05-10 8:46 ` George Dunlap
2016-05-12 8:04 ` Dario Faggioli
2016-05-09 16:17 ` Julien Grall
2016-05-09 16:56 ` Lars Kurth
2016-05-09 17:11 ` Julien Grall
2016-05-10 10:04 ` Stefano Stabellini
2016-05-10 1:12 ` Shannon Zhao
2016-05-09 17:14 ` Meng Xu
2016-05-09 17:37 ` Konrad Rzeszutek Wilk
2016-05-09 17:39 ` Lars Kurth
2016-05-10 2:53 ` Chun Yan Liu
2016-05-10 2:59 ` Doug Goldstein
2016-05-10 7:50 ` Dario Faggioli [this message]
2016-05-10 14:31 ` Lars Kurth
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=1462866603.4858.17.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=cardoe@cardoe.com \
--cc=lars.kurth.xen@gmail.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).