From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762333Ab3IDLU2 (ORCPT ); Wed, 4 Sep 2013 07:20:28 -0400 Received: from intranet.asianux.com ([58.214.24.6]:23216 "EHLO intranet.asianux.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756214Ab3IDLU1 (ORCPT ); Wed, 4 Sep 2013 07:20:27 -0400 X-Spam-Score: -100.9 Message-ID: <52271737.5040002@asianux.com> Date: Wed, 04 Sep 2013 19:19:19 +0800 From: Chen Gang User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130110 Thunderbird/17.0.2 MIME-Version: 1.0 To: Geert Uytterhoeven CC: Jiri Kosina , Paul McKenney , "dhowells@redhat.com" , Thomas Gleixner , Dave Jones , Arnd Bergmann , David Miller , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH trivial] UAPI: Kbuild: add/modify comments for "uapi/Kbuild" and "uapi/linux/Kbuild" References: <52005571.4080704@asianux.com> <52268800.2010200@asianux.com> <5226EAAE.6090500@asianux.com> <5226F9BF.8040304@asianux.com> <5226FF86.6030504@asianux.com> In-Reply-To: <5226FF86.6030504@asianux.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/04/2013 05:38 PM, Chen Gang wrote: > On 09/04/2013 05:27 PM, Geert Uytterhoeven wrote: >> On Wed, Sep 4, 2013 at 11:13 AM, Chen Gang 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 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/*". > Hmm... if "uapi/*" are really only for compatible, better to keep them no touch, that means: should always add new file(or directory) under "uapi/linux/" sub-directory (even if they are related with "uapi/*"). Thanks. > 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