From: Michal Marek <mmarek@suse.cz>
To: "H. Peter Anvin" <hpa@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, kbuild@vger.kernel.org,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, "H.J. Lu" <hjl.tools@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Sam Ravnborg <sam@ravnborg.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH 1/8] kbuild: Add support for installing generated asm headers
Date: Mon, 21 Nov 2011 18:27:07 +0100 [thread overview]
Message-ID: <4ECA89EB.2060604@suse.cz> (raw)
In-Reply-To: <1321569446-20433-2-git-send-email-hpa@linux.intel.com>
Dne 17.11.2011 23:37, H. Peter Anvin napsal(a):
> From: "H. Peter Anvin" <hpa@linux.intel.com>
>
> Generated asm headers are supposed to live in
> arch/*/include/generated/asm, but objhdr-y expect them to live in the
> same directory they are generated in. Instead of trying to cut that
> particular Gordian knot, introduce genhdr-y that takes this into
> account; the sole user of objhdr-y, linux/version.h, should be
> migrated over at some later date.
>
> Suggested-by: David Woodhouse <dwmw2@infradead.org>
> Acked-by: David Woodhouse <dwmw2@infradead.org>
> Cc: Sam Ravnborg <sam@ravnborg.org>
> Cc: Michal Marek <mmarek@suse.cz>
> Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
Acked-by: Michal Marek <mmarek@suse.cz>
next prev parent reply other threads:[~2011-11-21 17:26 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 [this message]
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:x86/syscall] kbuild, headers.sh: Don't make archheaders explicitly tip-bot for H. Peter Anvin
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=4ECA89EB.2060604@suse.cz \
--to=mmarek@suse.cz \
--cc=dwmw2@infradead.org \
--cc=geert@linux-m68k.org \
--cc=hjl.tools@gmail.com \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--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).