From: Sam Ravnborg <sam@ravnborg.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Adrian Bunk <bunk@kernel.org>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Avi Kivity <avi@qumranet.com>,
linux-arch@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] remove dummy asm/kvm.h files
Date: Tue, 1 Jul 2008 22:09:10 +0200 [thread overview]
Message-ID: <20080701200910.GA10677@uranus.ravnborg.org> (raw)
In-Reply-To: <1214942000.10393.418.camel@pmac.infradead.org>
On Tue, Jul 01, 2008 at 08:53:20PM +0100, David Woodhouse wrote:
> On Tue, 2008-07-01 at 21:32 +0200, Sam Ravnborg wrote:
> > On Tue, Jul 01, 2008 at 07:27:16PM +0300, Adrian Bunk wrote:
> > > This patch removes the dummy asm/kvm.h files on architectures not (yet)
> > > supporting KVM and uses the same conditional headers installation as
> > > already used for a.out.h .
> > >
> > > Also removed are superfluous install rules in the s390 and x86 Kbuild
> > > files (they are already in Kbuild.asm).
> > >
> > > Signed-off-by: Adrian Bunk <bunk@kernel.org>
> >
> > I really do not like the way we implement these checks and
> > think this should be a kconfig option.
> > But we do not (yet) require a configured kernel when exporting
> > to userspace so this is not feasible right now.
>
> I'm _really_ dubious about doing this kind of thing through Kconfig.
>
> In the general case, we really don't want exported headers to have any
> differences based on the kernel configuration.
>
> Yes, I suppose it would be OK if we are very careful not to let anyone
> use config symbols that aren't hard-coded for the given architecture.
> But in practice I don't think there's any real chance that we'd manage
> to be careful _enough_. We'd find people using symbols they shouldn't
> be.
We have two cases now and I think we can manage it.
But if we have only a few cases then we can also accept use of ARCH.
>
> > So despite the above this patch has my:
> > Acked-by: Sam Ravnborg <sam@ravnborg.org>
> >
> > Same for the asm/a.out patch you posted the other day.
> >
> > David - I assume you take these via your tree?
>
> I can do.
Thanks,
Sam
next prev parent reply other threads:[~2008-07-01 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 16:27 [2.6 patch] remove dummy asm/kvm.h files Adrian Bunk
2008-07-01 19:32 ` Sam Ravnborg
2008-07-01 19:53 ` David Woodhouse
2008-07-01 20:09 ` Sam Ravnborg [this message]
2008-07-02 7:38 ` Christian Borntraeger
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=20080701200910.GA10677@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=avi@qumranet.com \
--cc=borntraeger@de.ibm.com \
--cc=bunk@kernel.org \
--cc=dwmw2@infradead.org \
--cc=kvm@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@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