From: Sam Ravnborg <sam@ravnborg.org>
To: Will Deacon <will.deacon@arm.com>
Cc: Avi Kivity <avi@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"geert@linux-m68k.org" <geert@linux-m68k.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] kbuild: kvm: make export of linux/kvm_para.h unconditional
Date: Fri, 3 Aug 2012 15:02:30 +0200 [thread overview]
Message-ID: <20120803130230.GA9812@merkur.ravnborg.org> (raw)
In-Reply-To: <20120803125144.GD26925@mudshark.cambridge.arm.com>
On Fri, Aug 03, 2012 at 01:51:44PM +0100, Will Deacon wrote:
> On Thu, Aug 02, 2012 at 09:29:11PM +0100, Sam Ravnborg wrote:
> > On Thu, Aug 02, 2012 at 05:19:20PM +0300, Avi Kivity wrote:
> > > Can you get it reviewed by someone who is familiar with this? This is
> > > probably the third fix for the this issue.
> >
> > IMO the patch is wrong.
> > Any use of wildcards in include/asm-generic/Kbuild.asm is wrong.
>
> I agree that the wildcard stuff is horrible but that's not something
> introduced by this patch. In fact, I'm removing those where there is an
> asm-generic header that can be used instead.
>
> > IMO include/asm-generic/Kbuild.asm is for generic header files
> > that ALL archs can use.
> >
> > If not ALL archs can use it, then the individual arch shall
> > specify the file explicit.
>
> In which case, we should probably fix the rules for kvm.h and a.out.h as
> well. Neither of these headers have asm-generic versions and I doubt this
> is possible, so the header-y lines should be done for each architecture
> exporting such a header, no?
>
> > I know we here hit a bad thing with the generic-y support,
> > where we miss a good way to add a file to a lot of archs
> > without editing a lot of files.
>
> If there isn't a generic version of the header, then yes, I guess you have
> to modify the architectures that want to export it.
>
> I'm happy to post an extra patch sorting out kvm.h and a.out.h if that's
> what's required to get headers building again.
IMO this is required to sort this out for good.
I will be happy to review your patches.
Sam
next prev parent reply other threads:[~2012-08-03 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 13:44 [PATCH] kbuild: kvm: make export of linux/kvm_para.h unconditional Will Deacon
2012-08-02 12:25 ` Will Deacon
2012-08-02 14:19 ` Avi Kivity
2012-08-02 20:29 ` Sam Ravnborg
2012-08-03 12:51 ` Will Deacon
2012-08-03 13:02 ` Sam Ravnborg [this message]
2012-08-03 13:11 ` Arnd Bergmann
2012-09-16 19:31 ` Geert Uytterhoeven
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=20120803130230.GA9812@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=will.deacon@arm.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).