From: Avi Kivity <avi@redhat.com>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: 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: Sun, 12 Jul 2009 11:00:32 +0300 [thread overview]
Message-ID: <4A599820.9030905@redhat.com> (raw)
In-Reply-To: <1247303928.2678.46.camel@ht.satnam>
On 07/11/2009 12:18 PM, Jaswinder Singh Rajput wrote:
> Hello all,
>
> As include/linux/*.h file count is going to reach 1000.
>
> We need to do some better techniques to reduce the number of files and
> add some hierarchy levels like sub directories where possible.
>
> Like atmel is not exporting to user-space we can easily do :
>
> include/linux/atmel-mci.h -> include/linux/atmel/mci.h
> include/linux/atmel_pdc.h -> include/linux/atmel/pdc.h
> include/linux/atmel-pwm-bl.h -> include/linux/atmel/pwm-bl.h
> include/linux/atmel_pwm.h -> include/linux/atmel/pwm.h
> include/linux/atmel_serial.h -> include/linux/atmel/serial.h
> include/linux/atmel-ssc.h -> include/linux/atmel/ssc.h
> include/linux/atmel_tc.h -> include/linux/atmel/tc.h
>
> Also these files are not exporting :
>
> include/linux/kvm_host.h -> include/linux/kvm/host.h
> include/linux/kvm_para.h -> include/linux/kvm/para.h
> include/linux/kvm_types.h -> include/linux/kvm/types.h
>
>
IMO a much better move is to place non-ABI files (and the #ifdef KERNEL
parts of ABI files) outside include/linux.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-07-12 7:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 9:18 [FIX REQUEST] Need better management for include/linux/*.h Jaswinder Singh Rajput
2009-07-12 8:00 ` Avi Kivity [this message]
2009-07-27 11:54 ` Haavard Skinnemoen
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=4A599820.9030905@redhat.com \
--to=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