From: Ingo Molnar <mingo@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: tglx@linutronix.de, x86@kernel.org, linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH 1/2] x86: Provide a comment in uapi/asm/hw_breakpoint.h
Date: Wed, 24 Oct 2012 13:19:59 +0200 [thread overview]
Message-ID: <20121024111959.GD13010@gmail.com> (raw)
In-Reply-To: <22333.1351077173@warthog.procyon.org.uk>
* David Howells <dhowells@redhat.com> wrote:
> Ingo Molnar <mingo@kernel.org> wrote:
>
> > Just wondering, have the tools/perf/ issues been solved in your
> > tree, are the x86 UAPI disintegration changes pullable?
>
> Did you have a look at the set of five patches I sent? I
> think those should fix up perf and building tools with O=, but
> I'm not sure whether we want the last two. From commits
> already made, I'm guessing that at least patch #4 should be
> made.
>
> Note that the disintegrate-x86 branch does not include any
> perf fixes. I can regenerate that with some or all of them,
> once I know what they will be.
Just wanted to inquire about the current status of it, as I'd
rather not pull anything that introduces breakages and is still
work in progress. Once it's all sorted out I'll have a look.
Arnaldo, what's your take on David's perf Makefile changes?
Thanks,
Ingo
next prev parent reply other threads:[~2012-10-24 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 12:05 [PATCH 1/2] x86: Provide a comment in uapi/asm/hw_breakpoint.h David Howells
2012-10-22 12:06 ` [PATCH 2/2] x86: Provide a comment in uapi/asm/setup.h David Howells
2012-10-24 10:35 ` [PATCH 1/2] x86: Provide a comment in uapi/asm/hw_breakpoint.h Ingo Molnar
2012-10-24 11:12 ` David Howells
2012-10-24 11:19 ` Ingo Molnar [this message]
2012-10-31 22:53 ` 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=20121024111959.GD13010@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@infradead.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.