[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8d589cb7-a687-4b99-a19d-67009c4b2ec0@zytor.com>
Date: Mon, 10 Mar 2025 19:17:43 -0700
From: Xin Li <xin@...or.com>
To: Masahiro Yamada <masahiroy@...nel.org>
Cc: linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org,
nathan@...nel.org, nicolas@...sle.eu, bp@...en8.de, hpa@...or.com,
sraithal@....com
Subject: Re: [PATCH v1 1/1] kbuild: Add "make headers" to "make help" output
On 3/10/2025 7:13 PM, Masahiro Yamada wrote:
> On Tue, Mar 11, 2025 at 10:52 AM Masahiro Yamada <masahiroy@...nel.org> wrote:
>>
>> On Mon, Mar 10, 2025 at 3:23 PM Xin Li <xin@...or.com> wrote:
>>>
>>> On 3/8/2025 7:12 AM, Masahiro Yamada wrote:
>>>> On Sat, Mar 8, 2025 at 1:05 PM Xin Li (Intel) <xin@...or.com> wrote:
>>>>>
>>>>> Meanwhile explicitly state that the headers are uapi headers.
>>>>
>>>> There are many internal-use targets, which are not documented in the
>>>> help message.
>>>> I assume this one is the case.
>>>>
>>>> If users want to install UAPI headers, 'headers_install' is
>>>> the user-visible interface and it is already documented.
>>>>
>>>>
>>>
>>> hpa and Boris prefer to add it, which I also agree. But ofc it's your
>>> call :)
>>>
>>> If you don't want to add help for "headers", it probably still makes
>>> sense to explicitly state that the headers are uapi headers, no?
>>>
>>> Thanks!
>>> Xin
>>
>>
>> If a help message for "headers" is desired, how about this?
>>
>> headers - Build read-to-install uapi headers in usr/include
>
>
>
>
> For clarification, the following is the rationale.
>
>
> Build Installation
> -------------------------------------
> vmlinux install
> modules modules_install
> dtbs dtbs_install
> headers headers_install
>
>
>
> In Kbuild, the Build and Installation are separate steps,
> since the latter usually requires the root permission.
>
Oh, I didn't realize, thanks for making it clear.
Xin
Powered by blists - more mailing lists