All of lore.kernel.org
 help / color / mirror / Atom feed
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 12:35:59 +0200	[thread overview]
Message-ID: <20121024103559.GB10691@gmail.com> (raw)
In-Reply-To: <20121022120558.14413.78980.stgit@warthog.procyon.org.uk>


* David Howells <dhowells@redhat.com> wrote:

> Provide a comment in the empty uapi/asm/hw_breakpoint.h to make sure that the
> patch program doesn't delete it.
> 
> However, should some part of asm/hw_breakpoint.h actually be exported here,
> or, possibly, should the entire uapi file be removed?  In v3.6, though the
> file was marked for export to userspace, it had nothing outside of __KERNEL__.
> 
> This needs to be applied on top of the x86 UAPI disintegration patch.

Just wondering, have the tools/perf/ issues been solved in your 
tree, are the x86 UAPI disintegration changes pullable?

Thanks,

	Ingo

  parent reply	other threads:[~2012-10-24 10:36 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 ` Ingo Molnar [this message]
2012-10-24 11:12   ` [PATCH 1/2] x86: Provide a comment in uapi/asm/hw_breakpoint.h David Howells
2012-10-24 11:19     ` Ingo Molnar
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=20121024103559.GB10691@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.