From: Leo Yan <leo.yan@arm.com>
To: James Clark <james.clark@linaro.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] perf jevents: Fix build when there are other json files in the tree
Date: Mon, 20 Oct 2025 17:48:49 +0100 [thread overview]
Message-ID: <20251020164849.GJ281971@e132581.arm.com> (raw)
In-Reply-To: <20251020-james-perf-fix-json-find-v1-0-627b938ccf0d@linaro.org>
On Mon, Oct 20, 2025 at 05:08:25PM +0100, James Clark wrote:
> I hit this issue because I'm using clangd with a json compile database.
> Not sure if anyone else will actually hit this, but it's not impossible
> and the fix is trivial anyway. The first commit is the fix so has a tag.
> The other two commits are minor related cleanups.
I can reproduce the issue and the redundant warning, and confirmed
the series can fix them:
Tested-by: Leo Yan <leo.yan@arm.com>
next prev parent reply other threads:[~2025-10-20 16:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 16:08 [PATCH 0/3] perf jevents: Fix build when there are other json files in the tree James Clark
2025-10-20 16:08 ` [PATCH 1/3] " James Clark
2025-10-20 16:38 ` Leo Yan
2025-10-21 8:28 ` James Clark
2025-10-20 16:08 ` [PATCH 2/3] perf jevents: Remove unused makefile variable James Clark
2025-10-20 16:08 ` [PATCH 3/3] perf jevents: Suppress circular dependency warnings James Clark
2025-10-21 4:09 ` Namhyung Kim
2025-10-20 16:48 ` Leo Yan [this message]
2025-10-22 0:39 ` [PATCH 0/3] perf jevents: Fix build when there are other json files in the tree Namhyung Kim
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=20251020164849.GJ281971@e132581.arm.com \
--to=leo.yan@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.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).