linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
	Avi Kivity <avi@redhat.com>,
	Paul Gortmaker <paul.gortmaker@windriver.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Linux/m68k <linux-m68k@vger.kernel.org>,
	kvm@vger.kernel.org
Subject: Re: asm/kvm_para.h from asm-generic (was: Re: linux-next: triage for April 19, 2012)
Date: Thu, 14 Jun 2012 12:29:49 +0900	[thread overview]
Message-ID: <20120614032948.GD27673@linux-sh.org> (raw)
In-Reply-To: <CAMuHMdVM3zn_OUAtGTV_O0d3yFWBM5b_6ORHxaMLVE27Cf_XrQ@mail.gmail.com>

On Wed, Jun 13, 2012 at 02:46:32PM +0200, Geert Uytterhoeven wrote:
> There's a similar rule for kvm_para.h:
> 
> ifneq ($(wildcard $(srctree)/arch/$(SRCARCH)/include/asm/kvm_para.h \
>                   $(srctree)/include/asm-$(SRCARCH)/kvm_para.h),)
> header-y  += kvm_para.h
> endif
> 
> It's this rule that's now biting m68k, as it no longer works when using
> arch/*/include/asm/Kbuild to import <asm-generic/kvm_para.h>.
> (I guess it'll bite SH soon, too).
> 
So it did, thanks for catching it, today looks to be chock full of header
excitement.

> I found two ways to fix it:
>   1. Remove the "ifneq" above from include/asm-generic/Kbuild.asm,
>      so kvm_para.h is exported unconditionally.
>      Note that this breaks m32r and cris, as they don't have
> asm/kvm_para.h yet),
>    2. Add a similar "ifneq" to include/asm-generic/Kbuild, to make
>      the export of <linux/kvm_para.h> conditional.
>      I guess we want to remove all "dummy" kvm_para.h again, too?
> 
m32r and cris are broken at the moment anyways because they were
overlooked to begin with, so stubbing in generic-y += kvm_para.h rules
there should be sufficient. Presumably with those in place it should be
possible to kill off the wildcarding and just have it exported
unconditionally, as per your initial fix.

As to the merit of exporting a header with nothing in it to userspace,
Avi will have to figure that one out.

  parent reply	other threads:[~2012-06-14  3:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 21:07 asm/kvm_para.h from asm-generic (was: Re: linux-next: triage for April 19, 2012) Geert Uytterhoeven
2012-06-13 12:46 ` Geert Uytterhoeven
2012-06-13 12:49   ` Geert Uytterhoeven
2012-06-14  3:29   ` Paul Mundt [this message]
2012-06-19 18:48   ` Sam Ravnborg
2012-06-19 19:00     ` Sam Ravnborg

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=20120614032948.GD27673@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=avi@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    /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;
as well as URLs for NNTP newsgroup(s).