linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: namhyung@kernel.org, irogers@google.com,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf llvm-add2line: Remove unused include
Date: Wed, 8 Jan 2025 17:39:01 -0300	[thread overview]
Message-ID: <Z37iZZm3Ev2UnDA-@x1> (raw)
In-Reply-To: <20250108070248.237943-1-dvyukov@google.com>

On Wed, Jan 08, 2025 at 08:02:28AM +0100, Dmitry Vyukov wrote:
> Remove unused symbol_conf.h include.
> First, it's just unused. Second, it's problematic since this is a C++ file,
> and most perf headers don't compile as C++. So if any other includes are
> added to symbol_conf.h, it may break the build.

Thanks, applied to perf-tools-next,

- Arnaldo
 
> Signed-off-by: Dmitry Vyukov <dvyukov@google.com>
> Cc: Namhyung Kim <namhyung@kernel.org>
> Cc: Ian Rogers <irogers@google.com>
> Cc: linux-perf-users@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> ---
>  tools/perf/util/llvm-c-helpers.cpp | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/tools/perf/util/llvm-c-helpers.cpp b/tools/perf/util/llvm-c-helpers.cpp
> index 663bcaba2041f..004081bd12c9c 100644
> --- a/tools/perf/util/llvm-c-helpers.cpp
> +++ b/tools/perf/util/llvm-c-helpers.cpp
> @@ -18,7 +18,6 @@
>  extern "C" {
>  #include <linux/zalloc.h>
>  }
> -#include "symbol_conf.h"
>  #include "llvm-c-helpers.h"
>  
>  extern "C"
> 
> base-commit: 09a0fa92e5b45e99cf435b2fbf5ebcf889cf8780
> -- 
> 2.47.1.613.gc27f4b7a9f-goog
> 

      reply	other threads:[~2025-01-08 20:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08  7:02 [PATCH] perf llvm-add2line: Remove unused include Dmitry Vyukov
2025-01-08 20:39 ` Arnaldo Carvalho de Melo [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=Z37iZZm3Ev2UnDA-@x1 \
    --to=acme@kernel.org \
    --cc=dvyukov@google.com \
    --cc=irogers@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).