From: David Howells <dhowells@redhat.com>
Cc: dhowells@redhat.com, mingo@kernel.org, tglx@linutronix.de,
acme@ghostprotocols.net, bp@alien8.de, namhyung@gmail.com,
torvalds@linux-foundation.org, paulus@samba.org,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: Re: tools, perf: Fix up for x86 UAPI disintegration
Date: Mon, 05 Nov 2012 22:53:27 +0000 [thread overview]
Message-ID: <25722.1352156007@warthog.procyon.org.uk> (raw)
In-Reply-To: <15094.1352155791@warthog.procyon.org.uk>
David Howells <dhowells@redhat.com> wrote:
> I've posted a revised version of my perf patches to my UAPI disintegration GIT
> tree.
Hmmm... It seems to break some things according to Fengguang's kbuild test
robot.
David
next prev parent reply other threads:[~2012-11-05 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 22:49 tools, perf: Fix up for x86 UAPI disintegration David Howells
2012-11-05 22:49 ` David Howells
2012-11-05 22:53 ` David Howells [this message]
2012-11-05 23:18 ` David Howells
2012-11-07 8:55 ` Namhyung Kim
2012-11-07 11:01 ` 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=25722.1352156007@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=acme@ghostprotocols.net \
--cc=bp@alien8.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@gmail.com \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--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 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).