From: Borislav Petkov <bp@alien8.de>
To: Antonio Borneo <borneo.antonio@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/platform: fix "make O=dir kvmconfig"
Date: Sun, 13 Apr 2014 13:47:54 +0200 [thread overview]
Message-ID: <20140413114754.GC25088@pd.tnic> (raw)
In-Reply-To: <1397377568-8375-1-git-send-email-borneo.antonio@gmail.com>
On Sun, Apr 13, 2014 at 04:26:08PM +0800, Antonio Borneo wrote:
> Running:
> make O=dir x86_64_defconfig
> make O=dir kvmconfig
> the second command dirties the source tree with file ".config",
> symlink "source" and objects in folder "scripts".
>
> Fixed by adding paths in arch Makefile.
>
> Signed-off-by: Antonio Borneo <borneo.antonio@gmail.com>
Yes, without this patch and building into another dir with O=, kvmconfig
has more problems:
$ make O=/tmp/kernel kvmconfig
Using /tmp/kernel/.config as base
Merging arch/x86/configs/kvm_guest.config
sed: can't read arch/x86/configs/kvm_guest.config: No such file or directory
cat: arch/x86/configs/kvm_guest.config: No such file or directory
#
# merged configuration written to /tmp/kernel/.config (needs make)
#
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --oldconfig Kconfig
#
# configuration written to .config
So, yes, we want it:
Acked-by: Borislav Petkov <bp@suse.de>
Thanks.
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--
next prev parent reply other threads:[~2014-04-13 11:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 8:26 Antonio Borneo
2014-04-13 11:47 ` Borislav Petkov [this message]
2014-04-14 7:22 ` [tip:x86/urgent] x86/platform: Fix " tip-bot for Antonio Borneo
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=20140413114754.GC25088@pd.tnic \
--to=bp@alien8.de \
--cc=borneo.antonio@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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
Powered by JetHome