mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Sam Ravnborg <sam@ravnborg.org>, David Woodhouse <dwmw2@infradead.org>
Cc: Michal Marek <mmarek@suse.cz>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] kbuild: introduce ARCH_LIST for headers_install_all
Date: Fri, 5 Nov 2010 11:01:56 +0200	[thread overview]
Message-ID: <20101105090156.GA11777@shutemov.name> (raw)
In-Reply-To: <1288357441-23100-1-git-send-email-kirill@shutemov.name>

Does anybody care?

On Fri, Oct 29, 2010 at 04:04:00PM +0300, Kirill A. Shutsemov wrote:
> From: Kirill A. Shutemov <kirill@shutemov.name>
> 
> Using ARCH_LIST you can specify subset of architectures you want to get
> headers for.
> 
> Signed-off-by: Kirill A. Shutemov <kirill@shutemov.name>
> ---
>  Documentation/make/headers_install.txt |    5 +++--
>  scripts/headers.sh                     |    2 +-
>  2 files changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/make/headers_install.txt b/Documentation/make/headers_install.txt
> index f2481ca..1abace6 100644
> --- a/Documentation/make/headers_install.txt
> +++ b/Documentation/make/headers_install.txt
> @@ -39,8 +39,9 @@ INSTALL_HDR_PATH indicates where to install the headers.  It defaults to
>  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.)  Remember to provide the appropriate linux/asm directory via "mv"
> -or "ln -s" before building a C library with headers exported this way.
> +directory.)  You also can use ARCH_LIST to specify list of architectures.
> +Remember to provide the appropriate linux/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
>  <dwmw2@infradead.org>.
> diff --git a/scripts/headers.sh b/scripts/headers.sh
> index 1ddcdd3..62bc527 100755
> --- a/scripts/headers.sh
> +++ b/scripts/headers.sh
> @@ -13,7 +13,7 @@ do_command()
>  	fi
>  }
>  
> -archs=$(ls ${srctree}/arch)
> +archs=${ARCH_LIST:-$(ls ${srctree}/arch)}
>  
>  for arch in ${archs}; do
>  	case ${arch} in
> -- 
> 1.7.3.2
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
 Kirill A. Shutemov

  parent reply	other threads:[~2010-11-05  9:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29 13:04 Kirill A. Shutsemov
2010-10-29 13:04 ` [PATCH 2/2] kbuild: export linux/{a.out,kvm,kvm_para}.h on headers_install_all Kirill A. Shutsemov
2010-11-05  9:01 ` Kirill A. Shutemov [this message]
2010-11-07  7:58 ` [PATCH 1/2] kbuild: introduce ARCH_LIST for headers_install_all Américo Wang
2010-11-10 23:19   ` [PATCH] kbuild: introduce HDR_ARCH_LIST " Kirill A. Shutsemov

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=20101105090156.GA11777@shutemov.name \
    --to=kirill@shutemov.name \
    --cc=dwmw2@infradead.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    --cc=sam@ravnborg.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

all inboxes | Powered by JetHome®