All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Doug Goldstein <cardoe@cardoe.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel@lists.xen.org
Subject: Re: Kbuild and Kconfig
Date: Fri, 4 Sep 2015 12:54:28 +0100	[thread overview]
Message-ID: <alpine.DEB.2.02.1509041253410.2672@kaball.uk.xensource.com> (raw)
In-Reply-To: <55E75BD3.5080002@cardoe.com>

On Wed, 2 Sep 2015, Doug Goldstein wrote:
> Long term, yes we can tackle tools and stubdoms as well but initially I
> was trying to eat the elephant one bite at a time. My idea was that we
> would do xen/ first and you would have to go into that directory and run
> "make defconfig/menuconfig/config/etc && make" inside that directory.
> Once the other directories got converted we could move the setup to the
> top level and include xen/, tools/, stubdom/. It should be mostly a
> mechanical move.

FYI I would like to remove the QEMU, SeaBIOS, OVMF and stubdoms builds
from xen-unstable completely and rely on raisin to build them:

http://www.slideshare.net/StefanoStabellini/xds15-project-raisin
git://xenbits.xen.org/raisin.git

  parent reply	other threads:[~2015-09-04 11:54 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-02 17:50 Kbuild and Kconfig Doug Goldstein
2015-09-02 18:29 ` Andrew Cooper
2015-09-02 20:28   ` Doug Goldstein
2015-09-02 20:50     ` Andrew Cooper
2015-09-04 11:54     ` Stefano Stabellini [this message]
2015-09-03  9:56   ` Ian Campbell
2015-09-03 10:09     ` Tim Deegan
2015-09-03 10:26       ` Jan Beulich
2015-09-03 13:58     ` Doug Goldstein
2015-09-04 10:59     ` Andrew Cooper
2015-09-04 11:37       ` Ian Campbell
2015-09-03  9:56 ` Tim Deegan
2015-09-03 14:13   ` Doug Goldstein
2015-09-03 10:31 ` Jan Beulich
2015-09-03 14:04   ` Doug Goldstein
2015-09-03 15:00     ` Jan Beulich
2015-09-18 19:31       ` Doug Goldstein
2015-09-21  8:01         ` Jan Beulich

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=alpine.DEB.2.02.1509041253410.2672@kaball.uk.xensource.com \
    --to=stefano.stabellini@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=cardoe@cardoe.com \
    --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 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.