All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Stewart Hildebrand <stewart.hildebrand@dornerworks.com>
Cc: xen-devel@lists.xenproject.org, Doug Goldstein <cardoe@cardoe.com>
Subject: Re: [XEN PATCH 0/2] xen/build: fix kconfig errors during config merge
Date: Fri, 15 May 2020 15:19:57 +0100	[thread overview]
Message-ID: <20200515141957.GK2116@perard.uk.xensource.com> (raw)
In-Reply-To: <20200512175206.20314-1-stewart.hildebrand@dornerworks.com>

On Tue, May 12, 2020 at 01:52:04PM -0400, Stewart Hildebrand wrote:
> 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

Thanks for the patches.

FYI, `make defconfig custom.config` doesn't work as expected with the Xen
build system, it doesn't deal with this use case like Linux's one does.
There is no guaranty that "defconfig" will be made before "custom.config".
It would be better to run `make defconfig && make custom.config`, or
maybe use -j1, until this is properly handled. That's what is done by
kbuild.

Cheers,

-- 
Anthony PERARD


  parent reply	other threads:[~2020-05-15 14:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-12 17:52 [XEN PATCH 0/2] xen/build: fix kconfig errors during config merge Stewart Hildebrand
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 ` Anthony PERARD [this message]
2020-05-15 18:25 ` [XEN PATCH v2] " 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=20200515141957.GK2116@perard.uk.xensource.com \
    --to=anthony.perard@citrix.com \
    --cc=cardoe@cardoe.com \
    --cc=stewart.hildebrand@dornerworks.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.