From: Michal Marek <mmarek@suse.cz>
To: Yann Droneaud <ydroneaud@opteya.com>, linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
"Kirill A. Shutemov" <kirill@shutemov.name>,
David Woodhouse <dwmw2@infradead.org>,
Rob Landley <rob@landley.net>, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] Documentation/make/headers_install.txt: update documentation
Date: Thu, 03 Jul 2014 23:12:20 +0200 [thread overview]
Message-ID: <53B5C734.9020507@suse.cz> (raw)
In-Reply-To: <1404155479-5638-1-git-send-email-ydroneaud@opteya.com>
Dne 30.6.2014 21:11, Yann Droneaud napsal(a):
> Documentation in make/headers_install.txt is not
> up to date regarding:
> - way to list the various architectures;
> - path where the headers are installed.
>
> This patch try to fix these issues.
>
> Cc: Kirill A. Shutemov <kirill@shutemov.name>
> Cc: Michal Marek <mmarek@suse.cz>
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Rob Landley <rob@landley.net>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Signed-off-by: Yann Droneaud <ydroneaud@opteya.com>
> ---
> Documentation/make/headers_install.txt | 15 ++++++++-------
I have never noticed this file :). How about moving it to
Documentation/kbuild?
> 1 file changed, 8 insertions(+), 7 deletions(-)
>
> diff --git a/Documentation/make/headers_install.txt b/Documentation/make/headers_install.txt
> index 951eb9f1e040..8b6751f10dd3 100644
> --- a/Documentation/make/headers_install.txt
> +++ b/Documentation/make/headers_install.txt
> @@ -24,23 +24,24 @@ The "make headers_install" command can be run in the top level directory of the
> kernel source code (or using a standard out-of-tree build). It takes two
> optional arguments:
>
> - make headers_install ARCH=i386 INSTALL_HDR_PATH=/usr/include
> + make headers_install ARCH=i386 INSTALL_HDR_PATH=/usr
ARCH=x86 maybe?
> ARCH indicates which architecture to produce headers for, and defaults to the
> -current architecture. The linux/asm directory of the exported kernel headers
> -is platform-specific, to see a complete list of supported architectures use
> +current architecture. The asm/ directory of the exported kernel headers
> +is platform-specific, to see a list of supported architectures use
> the command:
>
> - ls -d include/asm-* | sed 's/.*-//'
> + /bin/ls -1 arch/*/include/asm/Kbuild | sed -e 's,^arch/,,' \
> + -e 's,/include/asm/Kbuild$,,'
Or, more simply, 'ls arch/'.
> -INSTALL_HDR_PATH indicates where to install the headers. It defaults to
> -"./usr/include".
> +INSTALL_HDR_PATH indicates where to create include/ directory to install the
> +headers. It defaults to "./usr/".
>
> The command "make headers_install_all" exports headers for all architectures
> simultaneously. (This is mostly of interest to distribution maintainers,
> who create an architecture-independent tarball from the resulting include
> directory.) You also can use HDR_ARCH_LIST to specify list of architectures.
> -Remember to provide the appropriate linux/asm directory via "mv" or "ln -s"
> +Remember to provide the appropriate asm/ directory via "mv" or "ln -s"
> before building a C library with headers exported this way.
>
> The kernel header export infrastructure is maintained by David Woodhouse
>
Looks good,
Thanks,
Michal
next prev parent reply other threads:[~2014-07-03 21:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 19:11 [PATCH] Documentation/make/headers_install.txt: update documentation Yann Droneaud
2014-07-03 21:12 ` Michal Marek [this message]
2014-07-09 20:49 ` Sam Ravnborg
2014-07-13 10:15 ` [PATCHv1 0/2] Documentation: move and update headers_install.txt Yann Droneaud
2014-07-13 10:15 ` [PATCHv1 1/2] Documentation: headers_install.txt is part of kbuild Yann Droneaud
2014-07-13 21:18 ` Sam Ravnborg
2014-08-05 14:08 ` Michal Marek
2014-07-13 10:15 ` [PATCHv1 2/2] Documentation/kbuild/headers_install.txt: update documentation Yann Droneaud
2014-07-13 21:26 ` Sam Ravnborg
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=53B5C734.9020507@suse.cz \
--to=mmarek@suse.cz \
--cc=dwmw2@infradead.org \
--cc=kirill@shutemov.name \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@landley.net \
--cc=sam@ravnborg.org \
--cc=ydroneaud@opteya.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;
as well as URLs for NNTP newsgroup(s).