From: David Howells <dhowells@redhat.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: dhowells@redhat.com, torvalds@osdl.org, arnd@arndb.de,
hpa@zytor.com, alan@lxorguk.ukuu.org.uk, fengguang.wu@intel.com,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] User API Disintegrate: Preparatory patches
Date: Thu, 04 Oct 2012 18:36:46 +0100 [thread overview]
Message-ID: <29855.1349372206@warthog.procyon.org.uk> (raw)
In-Reply-To: <CAMuHMdUx6he0MdL5etO6pDrMgd=JZWsf1TZj5WevjSpFANCWRA@mail.gmail.com>
Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > include/linux/libfdt.h | 4 +-
>
> So what happened here?
>
> -#include "../../scripts/dtc/libfdt/fdt.h"
> -#include "../../scripts/dtc/libfdt/libfdt.h"
> +#include <>
> +#include <>
I didn't expect 'system' header files to be outside of include/ or
arch/*/include/, so the bit of perl I had to turn this into <...> quietly
malfunctioned when it stripped too much off of the front.
Out of interest, why aren't these in include/? The normal way seems to be to
point the tool build at the kernel headers, not the kernel build at the script
headers.
David
next prev parent reply other threads:[~2012-10-04 17:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 18:36 David Howells
2012-10-04 17:12 ` Geert Uytterhoeven
2012-10-04 17:36 ` David Howells [this message]
2012-10-17 8:42 ` James Hogan
2012-10-22 11:50 ` James Hogan
2012-11-01 10:41 ` UAPI for new arches (was Re: [GIT PULL] User API Disintegrate: Preparatory patches) Vineet Gupta
2012-11-08 12:38 ` David Howells
2012-11-08 14:36 ` David Howells
2012-11-08 15:07 ` David Howells
2012-11-08 18:21 ` Vineet Gupta
2012-11-08 23:19 ` David Howells
2012-11-12 10:57 ` [arc-linux-dev] " Vineet Gupta
2012-11-12 13:14 ` David Howells
2012-11-14 13:01 ` James Hogan
2012-11-14 16:28 ` David Howells
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=29855.1349372206@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arnd@arndb.de \
--cc=fengguang.wu@intel.com \
--cc=geert@linux-m68k.org \
--cc=hpa@zytor.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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®