From: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
To: Avi Kivity <avi@redhat.com>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
nicolas.ferre@atmel.com, hskinnemoen@atmel.com,
kvm <kvm@vger.kernel.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [FIX REQUEST] Need better management for include/linux/*.h
Date: Mon, 27 Jul 2009 13:54:51 +0200 [thread overview]
Message-ID: <20090727135451.0754ba6e@hskinnemoen-d830> (raw)
In-Reply-To: <4A599820.9030905@redhat.com>
Avi Kivity wrote:
> IMO a much better move is to place non-ABI files (and the #ifdef KERNEL
> parts of ABI files) outside include/linux.
How about adding a new include/soc directory and move them all there
(along with similar header files from other SoC vendors)?
Haavard
next prev parent reply other threads:[~2009-07-27 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 9:18 Jaswinder Singh Rajput
2009-07-12 8:00 ` Avi Kivity
2009-07-27 11:54 ` Haavard Skinnemoen [this message]
2009-07-12 8:51 ` Andi Kleen
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=20090727135451.0754ba6e@hskinnemoen-d830 \
--to=haavard.skinnemoen@atmel.com \
--cc=avi@redhat.com \
--cc=hskinnemoen@atmel.com \
--cc=jaswinder@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.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
all inboxes | Powered by JetHome®