All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stewart Hildebrand <stewart.hildebrand@dornerworks.com>
To: xen-devel@lists.xenproject.org
Cc: Anthony PERARD <anthony.perard@citrix.com>,
	Doug Goldstein <cardoe@cardoe.com>
Subject: [XEN PATCH 0/2] xen/build: fix kconfig errors during config merge
Date: Tue, 12 May 2020 13:52:04 -0400	[thread overview]
Message-ID: <20200512175206.20314-1-stewart.hildebrand@dornerworks.com> (raw)

This series fixes a couple of kconfig errors that I observed while
invoking a build with a defconfig and config fragment.

I invoked the build as follows:

cat > xen/arch/arm/configs/custom.config <<EOF
CONFIG_DEBUG=y
CONFIG_SCHED_ARINC653=y
CONFIG_EARLY_PRINTK_ZYNQMP=y
EOF
make -C xen XEN_TARGET_ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- defconfig custom.config
make XEN_TARGET_ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- dist-xen -j $(nproc)

Stewart Hildebrand (2):
  xen/build: fixup path to merge_config.sh
  xen/build: use the correct kconfig makefile

 xen/tools/kconfig/Makefile | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

-- 
2.26.2



             reply	other threads:[~2020-05-12 17:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 17:52 Stewart Hildebrand [this message]
2020-05-12 17:52 ` [XEN PATCH 1/2] xen/build: fixup path to merge_config.sh Stewart Hildebrand
2020-05-15 14:13   ` Anthony PERARD
2020-05-12 17:52 ` [XEN PATCH 2/2] xen/build: use the correct kconfig makefile Stewart Hildebrand
2020-05-15 14:51   ` Anthony PERARD
2020-05-15 14:19 ` [XEN PATCH 0/2] xen/build: fix kconfig errors during config merge Anthony PERARD
2020-05-15 18:25 ` [XEN PATCH v2] xen/build: use the correct kconfig makefile Stewart Hildebrand
2020-05-15 18:30   ` Stewart Hildebrand
2020-05-18  9:44   ` Anthony PERARD

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=20200512175206.20314-1-stewart.hildebrand@dornerworks.com \
    --to=stewart.hildebrand@dornerworks.com \
    --cc=anthony.perard@citrix.com \
    --cc=cardoe@cardoe.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 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.