Kernel KVM-PPC virtualization development
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH] kvm: external module: fix unifdef problem
Date: Sun, 26 Oct 2008 12:38:31 +0000	[thread overview]
Message-ID: <490464C7.1020804@redhat.com> (raw)
In-Reply-To: <1224871854.9634.50.camel@localhost.localdomain>

Hollis Blanchard wrote:
> Guys, I don't mind if you add new things that aren't enabled for other
> architectures, but please try to be a little more careful about breaking
> us.
>
> This patch results in the following on PowerPC:
>         mv $i $i.orig && unifdef -DCONFIG_POWERPC -UCONFIG_X86 IA64
>         $i.orig > $i; [ $? -le 2 ] && rm $i.orig; done
>         unifdef: can only do one file
>
>   

Aw.

> Here's my proposed fix:
>
> kvm: external module: Treat NONARCH_CONFIG as a list, not a single item.
>
> Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
>
> diff --git a/kernel/Makefile b/kernel/Makefile
> --- a/kernel/Makefile
> +++ b/kernel/Makefile
> @@ -25,8 +25,9 @@ _hack = mv $1 $1.orig && \
>  	gawk -v version=$(version) -f $(ARCH_DIR)/hack-module.awk $1.orig \
>  	    | sed '/\#include/! s/\blapic\b/l_apic/g' > $1 && rm $1.orig
>  
> +unifdef_uflags = $(foreach arch, $(NONARCH_CONFIG), -UCONFIG_$(arch))
>   

$(patsubst ...), or even $(NONARCH_CONFIG:%=-UCONFIG_%)

But I think NONARCH_CONFIG needs to be adjusted as well.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2008-10-26 12:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-24 18:10 [PATCH] kvm: external module: fix unifdef problem Hollis Blanchard
2008-10-26 12:38 ` Avi Kivity [this message]
2008-10-27  0:58 ` Sheng Yang
2008-10-27 16:07 ` Christian Ehrhardt
2008-10-27 16:29 ` Avi Kivity
2008-10-28  1:02 ` Zhang, Xiantao

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=490464C7.1020804@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm-ppc@vger.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