From: "tip-bot for H. Peter Anvin" <hpa@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
mmarek@suse.cz, tglx@linutronix.de
Subject: [tip:x86/syscall] kbuild, headers.sh: Don't make archheaders explicitly
Date: Tue, 22 Nov 2011 14:57:57 -0800 [thread overview]
Message-ID: <tip-9147621c771c8b6a5c8985373af3a8200e8b4a41@git.kernel.org> (raw)
In-Reply-To: <4ECA8991.20302@suse.cz>
Commit-ID: 9147621c771c8b6a5c8985373af3a8200e8b4a41
Gitweb: http://git.kernel.org/tip/9147621c771c8b6a5c8985373af3a8200e8b4a41
Author: H. Peter Anvin <hpa@zytor.com>
AuthorDate: Tue, 22 Nov 2011 14:47:50 -0800
Committer: H. Peter Anvin <hpa@zytor.com>
CommitDate: Tue, 22 Nov 2011 14:47:50 -0800
kbuild, headers.sh: Don't make archheaders explicitly
We don't need to explicitly invoke the archheaders target because of
the dependency on __headers in the Makefile.
Reported-and-tested-by: Michal Marek <mmarek@suse.cz>
Link: http://lkml.kernel.org/r/4ECA8991.20302@suse.cz
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
---
| 1 -
1 files changed, 0 insertions(+), 1 deletions(-)
--git a/scripts/headers.sh b/scripts/headers.sh
index af1ed88..978b42b 100755
--- a/scripts/headers.sh
+++ b/scripts/headers.sh
@@ -7,7 +7,6 @@ set -e
do_command()
{
if [ -f ${srctree}/arch/$2/include/asm/Kbuild ]; then
- make ARCH=$2 KBUILD_HEADERS=$1 archheaders
make ARCH=$2 KBUILD_HEADERS=$1 headers_$1
else
printf "Ignoring arch: %s\n" ${arch}
next prev parent reply other threads:[~2011-11-22 23:00 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-17 22:37 [PATCH 0/8] RFC x86: Generate system calls from a simple table H. Peter Anvin
2011-11-17 22:37 ` [PATCH 1/8] kbuild: Add support for installing generated asm headers H. Peter Anvin
2011-11-21 17:27 ` Michal Marek
2011-11-17 22:37 ` [PATCH 2/8] kbuild: Add support for an "archheaders" target H. Peter Anvin
2011-11-21 17:25 ` Michal Marek
2011-11-21 17:33 ` H. Peter Anvin
2011-11-21 20:03 ` Michal Marek
2011-11-22 22:57 ` tip-bot for H. Peter Anvin [this message]
2011-11-17 22:37 ` [PATCH 3/8] x86-64, syscall: Adjust comment spacing and remove typo H. Peter Anvin
2011-11-19 0:35 ` [tip:x86/syscall] x86, syscall: Re-fix typo in comment tip-bot for H. Peter Anvin
2011-11-17 22:37 ` [PATCH 4/8] x86-64, ia32: Move compat_ni_syscall into C and its own file H. Peter Anvin
2011-11-17 22:37 ` [PATCH 5/8] trace: Include <asm/asm-offsets.h> in trace_syscalls.c H. Peter Anvin
2011-11-17 22:42 ` Steven Rostedt
2011-11-17 22:44 ` H. Peter Anvin
2011-11-17 22:51 ` H. Peter Anvin
2011-11-17 22:37 ` [PATCH 6/8] x86: Machine-readable syscall tables and scripts to process them H. Peter Anvin
2011-11-18 22:15 ` Matt Helsley
2011-11-18 23:13 ` H. Peter Anvin
2011-11-19 0:34 ` [tip:x86/syscall] x86: Simplify syscallhdr.sh tip-bot for H. Peter Anvin
2011-11-19 1:07 ` [tip:x86/syscall] x86, syscall: Allow syscall offset to be symbolic tip-bot for H. Peter Anvin
2011-11-17 22:37 ` [PATCH 7/8] checksyscalls: Use arch/x86/syscalls/syscall_32.tbl as source H. Peter Anvin
2011-11-21 17:28 ` Michal Marek
2011-11-17 22:37 ` [PATCH 8/8] x86: Generate system call tables and unistd_*.h from tables H. Peter Anvin
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=tip-9147621c771c8b6a5c8985373af3a8200e8b4a41@git.kernel.org \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.cz \
--cc=tglx@linutronix.de \
/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).