From: David Howells <dhowells@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: dhowells@redhat.com,
Linus Torvalds <torvalds@linux-foundation.org>,
paulus@samba.org, davem@davemloft.net, jaxboe@fusionio.com,
tj@kernel.org, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] perf: Fix UAPI fallout
Date: Mon, 15 Oct 2012 09:56:22 +0100 [thread overview]
Message-ID: <13954.1350291382@warthog.procyon.org.uk> (raw)
In-Reply-To: <20121014085617.GA22544@gmail.com>
Ingo Molnar <mingo@kernel.org> wrote:
> Arnaldo: the way we include some of the include files directly
> into tools/perf/ .c files [such as hw_breakpoint.h] and
> represent others transparently via utils/include/ [such as
> rbtree.h] is a bit messy and ought to be cleaned up I suspect.
I tried to make the USERINCLUDE macro in the bottom-level Makefile that, but I
didn't realise I had to export it:-(.
That, however, also brings in linux/kconfig.h but I don't know whether you
want/need that.
> I think the best model would be to cleanly separate from any
> /usr/include/linux/ muck, which might be out of sync, and which
> might stand in the way of changes. Is it possible to exclude all
> of /usr/include/ and try to build purely from
> include/uapi/linux/
You would also need arch/foo/include/uapi/.
David
next prev parent reply other threads:[~2012-10-15 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-13 10:48 [GIT PULL] UAPI disintegration for include/linux/{,byteorder/}*.h David Howells
2012-10-14 0:34 ` Linus Torvalds
2012-10-14 8:56 ` [PATCH] perf: Fix UAPI fallout Ingo Molnar
2012-10-14 15:38 ` David Miller
2012-10-15 8:56 ` David Howells [this message]
2012-10-19 13:35 ` David Howells
2012-10-15 8:52 ` [GIT PULL] UAPI disintegration for include/linux/{,byteorder/}*.h 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=13954.1350291382@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=jaxboe@fusionio.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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