All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Vinson Lee <vlee@freedesktop.org>
Cc: trinity@vger.kernel.org, Vinson Lee <vlee@twitter.com>
Subject: Re: [PATCH] Fix build on kernels without perf_event_attr exclude_callchain_kernel.
Date: Fri, 24 May 2013 10:34:14 -0400	[thread overview]
Message-ID: <20130524143413.GC3106@redhat.com> (raw)
In-Reply-To: <1369368527-21362-1-git-send-email-vlee@freedesktop.org>

On Thu, May 23, 2013 at 09:08:47PM -0700, Vinson Lee wrote:
 > From: Vinson Lee <vlee@twitter.com>
 > 
 > This patch fixes these build errors on 3.6 and older.
 > 
 >   CC	syscalls/perf_event_open.o
 > syscalls/perf_event_open.c: In function ‘create_mostly_valid_counting_event’:
 > syscalls/perf_event_open.c:382:6: error: ‘struct perf_event_attr’ has no member named ‘exclude_callchain_kernel’
 > syscalls/perf_event_open.c:383:6: error: ‘struct perf_event_attr’ has no member named ‘exclude_callchain_user’
 > syscalls/perf_event_open.c: In function ‘create_mostly_valid_sampling_event’:
 > syscalls/perf_event_open.c:431:6: error: ‘struct perf_event_attr’ has no member named ‘exclude_callchain_kernel’
 > syscalls/perf_event_open.c:432:6: error: ‘struct perf_event_attr’ has no member named ‘exclude_callchain_user’
 > make: *** [syscalls/perf_event_open.o] Error 1
 > 
 > Signed-off-by: Vinson Lee <vlee@twitter.com>
 > ---
 >  configure.sh               |   26 ++++++++++++++++++++++++++
 >  syscalls/perf_event_open.c |    4 ++++
 >  2 files changed, 30 insertions(+)
 > 
 > diff --git a/configure.sh b/configure.sh
 > index e676418..4be1e59 100755
 > --- a/configure.sh
 > +++ b/configure.sh
 > @@ -182,6 +182,32 @@ else
 >  fi

thanks, applied.

	Dave

      reply	other threads:[~2013-05-24 14:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24  4:08 [PATCH] Fix build on kernels without perf_event_attr exclude_callchain_kernel Vinson Lee
2013-05-24 14:34 ` Dave Jones [this message]

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=20130524143413.GC3106@redhat.com \
    --to=davej@redhat.com \
    --cc=trinity@vger.kernel.org \
    --cc=vlee@freedesktop.org \
    --cc=vlee@twitter.com \
    /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.