From: Chen Gang <gang.chen@asianux.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jiri Kosina <trivial@kernel.org>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
"dhowells@redhat.com" <dhowells@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Dave Jones <davej@redhat.com>, Arnd Bergmann <arnd@arndb.de>,
David Miller <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH trivial] UAPI: Kbuild: add/modify comments for "uapi/Kbuild" and "uapi/linux/Kbuild"
Date: Wed, 04 Sep 2013 17:38:14 +0800 [thread overview]
Message-ID: <5226FF86.6030504@asianux.com> (raw)
In-Reply-To: <CAMuHMdWc3mtva92qDy4j6iUhQc5grHA1-5=vC4iXZoSyFxB4cw@mail.gmail.com>
On 09/04/2013 05:27 PM, Geert Uytterhoeven wrote:
> On Wed, Sep 4, 2013 at 11:13 AM, Chen Gang <gang.chen@asianux.com> wrote:
>>>> Hmm... why we need "uapi/linux/" ? (I can not find some related
>>>> documents, so I have to 'guess').
>>>
>>> The "uapi" subdirectories are there to distinguish userspace headers from
>>> kernelspace headers, and allow both to live in the kernel source tree.
>>>
>>> When running "make headers_install", the (processed) headers in the
>>> various "uapi" subdirectories are copied to /usr/include.
>>> Hence "uapi/linux/foo.h" becomes <linux/foo.h> in userspace.
>>> In userspace there are no "uapi" subdirectories anymore.
>>>
>>
>> Yeah, so why need another "uapi/*" excluding "uapi/linux" ?
>>
>> Are they also truly still "Userspace API" but which need not distinguish
>> ? (at least, it seems that idea is not quite good).
>>
>> Hmm... maybe the "uapi/*" except "uapi/linux" are also installed? Is it
>> for compatible (originally they are here, and now we have to follow, it
>> is no reason to change if not find related critical issues)?
>
> All uapi files are installed, a.o. /usr/include/scsi/, /usr/include/video/, ...
>
Oh, sorry, I misunderstand your original mail contents.
> Historically, everything under "include" in the kernel source tree was
> installed in /usr/include/, after (semi)manual cleanup.
> Since the uapi split, everything is handled automatically.
> Because of compatibility reasons (do not break userspace), paths had to
> stay the same.
>
At least for me, that sounds reasonable.
Hmm... when some members need add a new Userspace API. I guess:
if it is related with one of existent "uapi/*" sub-directory (except "uapi/linux"), they need put the file(or directory) under the related "uapi/*",
if can not find existent "uapi/*" sub-directory, they need put the file(or directory) under "uapi/linux/*".
Does it sound reasonable ?
Thanks.
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
>
>
--
Chen Gang
next prev parent reply other threads:[~2013-09-04 9:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-06 1:46 [PATCH trivial] UAPI: Kbuild: add/modify comments for "uapi/Kbuild" and "uapi/linux/Kbuild" Chen Gang
2013-08-06 17:31 ` Joe Perches
2013-08-07 2:42 ` Chen Gang
2013-08-07 7:32 ` Rob Landley
2013-08-07 8:48 ` Chen Gang
2013-08-08 2:13 ` Chen Gang
2013-08-21 6:34 ` Chen Gang
2013-08-23 10:30 ` Chen Gang
2013-09-03 5:57 ` Chen Gang
2013-09-05 0:46 ` [PATCH trivial v2] " Chen Gang
2013-09-05 1:05 ` Chen Gang
2013-09-05 1:09 ` [PATCH trivial v3] include/uapi/Kbuild: modify the comments for it Chen Gang
2013-10-01 2:19 ` Chen Gang
2013-10-01 3:21 ` [PATCH trivial v4] include/uapi/Kbuild: modify comment to provide summary descriptions for Linux UAPI Chen Gang
2013-09-03 16:41 ` [PATCH trivial] UAPI: Kbuild: add/modify comments for "uapi/Kbuild" and "uapi/linux/Kbuild" Geert Uytterhoeven
2013-09-04 1:08 ` Chen Gang
2013-09-04 7:02 ` Geert Uytterhoeven
2013-09-04 8:09 ` Chen Gang
2013-09-04 9:02 ` Geert Uytterhoeven
2013-09-04 9:13 ` Chen Gang
2013-09-04 9:27 ` Geert Uytterhoeven
2013-09-04 9:38 ` Chen Gang [this message]
2013-09-04 11:19 ` Chen Gang
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=5226FF86.6030504@asianux.com \
--to=gang.chen@asianux.com \
--cc=arnd@arndb.de \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=trivial@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