From: George Dunlap <george.dunlap@eu.citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
xen-devel@lists.xensource.com
Cc: george.dunlap@citrix.com
Subject: Re: [PATCH 5/5] raisin: build linux
Date: Tue, 21 Apr 2015 16:11:05 +0100 [thread overview]
Message-ID: <55366889.7000107@eu.citrix.com> (raw)
In-Reply-To: <1429628103-10979-5-git-send-email-stefano.stabellini@eu.citrix.com>
On 04/21/2015 03:55 PM, Stefano Stabellini wrote:
> Add a component, disabled by default, to build a linux kernel with the
> Xen kconfig options enabled.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Acked-by: George Dunlap <george.dunlap@eu.citrix.com>
I'm wondering if at some point we might want to give people the option
to pass in a specific Linux config; but that can be a feature for
another patch.
-George
prev parent reply other threads:[~2015-04-21 15:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 14:54 [PATCH 0/5] raisin: introduce ovmf and linux Stefano Stabellini
2015-04-21 14:54 ` [PATCH 1/5] raisin: introduce _verbose_echo Stefano Stabellini
2015-04-21 15:09 ` George Dunlap
2015-04-21 15:37 ` Stefano Stabellini
2015-04-21 14:55 ` [PATCH 2/5] raisin: remove duplicate source config in raise Stefano Stabellini
2015-04-21 15:09 ` George Dunlap
2015-04-21 15:42 ` Stefano Stabellini
2015-04-21 14:55 ` [PATCH 3/5] raisin: rename ARCH to RAISIN_ARCH Stefano Stabellini
2015-04-21 15:09 ` George Dunlap
2015-04-21 14:55 ` [PATCH 4/5] raisin: introduce ovmf Stefano Stabellini
2015-04-21 15:03 ` George Dunlap
2015-04-21 15:43 ` Stefano Stabellini
2015-04-21 15:45 ` George Dunlap
2015-04-21 15:46 ` George Dunlap
2015-04-21 14:55 ` [PATCH 5/5] raisin: build linux Stefano Stabellini
2015-04-21 15:11 ` George Dunlap [this message]
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=55366889.7000107@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=george.dunlap@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.