public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@kernel.org>,
	Namhyung Kim <namhyung@kernel.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Michael Petlan <mpetlan@redhat.com>
Subject: Re: [PATCH 1/5] tools: Add missing perf_event.h include
Date: Thu, 22 Aug 2019 11:13:48 -0300	[thread overview]
Message-ID: <20190822141348.GA29569@kernel.org> (raw)
In-Reply-To: <20190822111141.25823-2-jolsa@kernel.org>

Em Thu, Aug 22, 2019 at 01:11:37PM +0200, Jiri Olsa escreveu:
> We need perf_event.h include for 'struct perf_event_mmap_page'.
> 
> Link: http://lkml.kernel.org/n/tip-bolqkmqajexhccjb0ib0an8w@git.kernel.org

Thanks, applied.

- Arnaldo

> Signed-off-by: Jiri Olsa <jolsa@kernel.org>
> ---
>  tools/include/linux/ring_buffer.h | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/tools/include/linux/ring_buffer.h b/tools/include/linux/ring_buffer.h
> index 9a083ae60473..6c02617377c2 100644
> --- a/tools/include/linux/ring_buffer.h
> +++ b/tools/include/linux/ring_buffer.h
> @@ -2,6 +2,7 @@
>  #define _TOOLS_LINUX_RING_BUFFER_H_
>  
>  #include <asm/barrier.h>
> +#include <linux/perf_event.h>
>  
>  /*
>   * Contract with kernel for walking the perf ring buffer from
> -- 
> 2.21.0

-- 

- Arnaldo

  reply	other threads:[~2019-08-22 14:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-22 11:11 [PATCH 0/5] tools,libperf: Assorted fixes Jiri Olsa
2019-08-22 11:11 ` [PATCH 1/5] tools: Add missing perf_event.h include Jiri Olsa
2019-08-22 14:13   ` Arnaldo Carvalho de Melo [this message]
2019-08-22 11:11 ` [PATCH 2/5] libperf: Use perf_cpu_map__nr instead of cpu_map__nr Jiri Olsa
2019-08-22 11:11 ` [PATCH 3/5] libperf: Move cpu_map__empty to perf_cpu_map__empty Jiri Olsa
2019-08-23 12:21   ` [tip: perf/core] libperf: Move perf's cpu_map__empty() to perf_cpu_map__empty() tip-bot2 for Jiri Olsa
2019-08-22 11:11 ` [PATCH 4/5] libperf: Move cpu_map__idx to perf_cpu_map__idx Jiri Olsa
2019-08-23 12:21   ` [tip: perf/core] libperf: Move perf's cpu_map__idx() to perf_cpu_map__idx() tip-bot2 for Jiri Olsa
2019-08-22 11:11 ` [PATCH 5/5] libperf: Add perf_thread_map__nr/perf_thread_map__pid functions Jiri Olsa
2019-08-22 15:18   ` Arnaldo Carvalho de Melo
2019-08-23 12:29   ` [tip: perf/core] " tip-bot2 for Jiri Olsa

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=20190822141348.GA29569@kernel.org \
    --to=arnaldo.melo@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mpetlan@redhat.com \
    --cc=namhyung@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