All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: Leo Yan <leo.yan@arm.com>
Cc: linux-riscv@lists.infradead.org, acme@kernel.org,
	namhyung@kernel.org, jolsa@kernel.org, irogers@google.com,
	adrian.hunter@intel.com, nathan@kernel.org,
	nick.desaulniers+lkml@gmail.com, morbo@google.com,
	justinstitt@google.com, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	james.clark@linaro.org, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v3 0/9] perf build: Support building with Clang
Date: Fri, 10 Oct 2025 02:27:18 +0000	[thread overview]
Message-ID: <176006323800.354358.6110592426551858799.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251006-perf_build_android_ndk-v3-0-4305590795b2@arm.com>

Hello:

This series was applied to riscv/linux.git (fixes)
by Arnaldo Carvalho de Melo <acme@redhat.com>:

On Mon, 06 Oct 2025 17:21:22 +0100 you wrote:
> This series adds support for building perf with Clang, following the
> discussion in [1]. Because the Android NDK uses Clang by default,
> enabling Clang builds naturally covers Android as well.
> 
> The series is organized as follows:
> 
>   - Patches 1~2: Fix two bugs found with Clang.
>   - Patches 3~7: Correct CROSS_ARCH, Disable thread safety analysis for
>                  perl header, and dismiss Clang build warnings.
>   - Patches 8~9: Enable Clang in the Makefile and update the
>                  documentation.
> 
> [...]

Here is the summary with links:
  - [v3,1/9] tools build: Align warning options with perf
    https://git.kernel.org/riscv/c/53d067feb8c4
  - [v3,2/9] perf python: split Clang options when invoking Popen
    https://git.kernel.org/riscv/c/c6a43bc3e8f6
  - [v3,3/9] perf build: Correct CROSS_ARCH for clang
    https://git.kernel.org/riscv/c/ed33e5e43c1e
  - [v3,4/9] perf build: Disable thread safety analysis for perl header
    https://git.kernel.org/riscv/c/e7e86d7697c6
  - [v3,5/9] perf test coresight: Dismiss clang warning for memcpy thread
    https://git.kernel.org/riscv/c/50b7e7082a3d
  - [v3,6/9] perf test coresight: Dismiss clang warning for thread loop
    https://git.kernel.org/riscv/c/244a1ac76a67
  - [v3,7/9] perf test coresight: Dismiss clang warning for unroll loop thread
    https://git.kernel.org/riscv/c/9ec46fc93803
  - [v3,8/9] perf build: Support build with clang
    https://git.kernel.org/riscv/c/4772e66cb45e
  - [v3,9/9] perf docs: Document building with Clang
    https://git.kernel.org/riscv/c/0a75ba3e842c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Leo Yan <leo.yan@arm.com>
Cc: linux-riscv@lists.infradead.org, acme@kernel.org,
	namhyung@kernel.org, jolsa@kernel.org, irogers@google.com,
	adrian.hunter@intel.com, nathan@kernel.org,
	nick.desaulniers+lkml@gmail.com, morbo@google.com,
	justinstitt@google.com, paul.walmsley@sifive.com,
	palmer@dabbelt.com, aou@eecs.berkeley.edu, alex@ghiti.fr,
	james.clark@linaro.org, linux-kernel@vger.kernel.org,
	linux-perf-users@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH v3 0/9] perf build: Support building with Clang
Date: Fri, 10 Oct 2025 02:27:18 +0000	[thread overview]
Message-ID: <176006323800.354358.6110592426551858799.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251006-perf_build_android_ndk-v3-0-4305590795b2@arm.com>

Hello:

This series was applied to riscv/linux.git (fixes)
by Arnaldo Carvalho de Melo <acme@redhat.com>:

On Mon, 06 Oct 2025 17:21:22 +0100 you wrote:
> This series adds support for building perf with Clang, following the
> discussion in [1]. Because the Android NDK uses Clang by default,
> enabling Clang builds naturally covers Android as well.
> 
> The series is organized as follows:
> 
>   - Patches 1~2: Fix two bugs found with Clang.
>   - Patches 3~7: Correct CROSS_ARCH, Disable thread safety analysis for
>                  perl header, and dismiss Clang build warnings.
>   - Patches 8~9: Enable Clang in the Makefile and update the
>                  documentation.
> 
> [...]

Here is the summary with links:
  - [v3,1/9] tools build: Align warning options with perf
    https://git.kernel.org/riscv/c/53d067feb8c4
  - [v3,2/9] perf python: split Clang options when invoking Popen
    https://git.kernel.org/riscv/c/c6a43bc3e8f6
  - [v3,3/9] perf build: Correct CROSS_ARCH for clang
    https://git.kernel.org/riscv/c/ed33e5e43c1e
  - [v3,4/9] perf build: Disable thread safety analysis for perl header
    https://git.kernel.org/riscv/c/e7e86d7697c6
  - [v3,5/9] perf test coresight: Dismiss clang warning for memcpy thread
    https://git.kernel.org/riscv/c/50b7e7082a3d
  - [v3,6/9] perf test coresight: Dismiss clang warning for thread loop
    https://git.kernel.org/riscv/c/244a1ac76a67
  - [v3,7/9] perf test coresight: Dismiss clang warning for unroll loop thread
    https://git.kernel.org/riscv/c/9ec46fc93803
  - [v3,8/9] perf build: Support build with clang
    https://git.kernel.org/riscv/c/4772e66cb45e
  - [v3,9/9] perf docs: Document building with Clang
    https://git.kernel.org/riscv/c/0a75ba3e842c

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  parent reply	other threads:[~2025-10-10  2:27 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06 16:21 [PATCH v3 0/9] perf build: Support building with Clang Leo Yan
2025-10-06 16:21 ` Leo Yan
2025-10-06 16:21 ` [PATCH v3 1/9] tools build: Align warning options with perf Leo Yan
2025-10-06 16:21   ` Leo Yan
2025-10-06 16:21 ` [PATCH v3 2/9] perf python: split Clang options when invoking Popen Leo Yan
2025-10-06 16:21   ` Leo Yan
2025-10-06 16:21 ` [PATCH v3 3/9] perf build: Correct CROSS_ARCH for clang Leo Yan
2025-10-06 16:21   ` Leo Yan
2025-10-06 16:21 ` [PATCH v3 4/9] perf build: Disable thread safety analysis for perl header Leo Yan
2025-10-06 16:21   ` Leo Yan
2025-10-06 17:56   ` Ian Rogers
2025-10-06 17:56     ` Ian Rogers
2025-10-06 18:48     ` Arnaldo Carvalho de Melo
2025-10-06 18:48       ` Arnaldo Carvalho de Melo
2025-10-06 16:21 ` [PATCH v3 5/9] perf test coresight: Dismiss clang warning for memcpy thread Leo Yan
2025-10-06 16:21   ` Leo Yan
2025-10-06 16:21 ` [PATCH v3 6/9] perf test coresight: Dismiss clang warning for thread loop Leo Yan
2025-10-06 16:21   ` Leo Yan
2025-10-06 16:21 ` [PATCH v3 7/9] perf test coresight: Dismiss clang warning for unroll loop thread Leo Yan
2025-10-06 16:21   ` Leo Yan
2025-10-06 16:21 ` [PATCH v3 8/9] perf build: Support build with clang Leo Yan
2025-10-06 16:21   ` Leo Yan
2025-10-06 16:21 ` [PATCH v3 9/9] perf docs: Document building with Clang Leo Yan
2025-10-06 16:21   ` Leo Yan
2025-10-06 17:57 ` [PATCH v3 0/9] perf build: Support " Ian Rogers
2025-10-06 17:57   ` Ian Rogers
2025-10-06 18:50 ` Arnaldo Carvalho de Melo
2025-10-06 18:50   ` Arnaldo Carvalho de Melo
2025-10-07 18:06   ` Leo Yan
2025-10-07 18:06     ` Leo Yan
2025-10-06 19:50 ` Arnaldo Carvalho de Melo
2025-10-06 19:50   ` Arnaldo Carvalho de Melo
2025-10-10  2:27 ` patchwork-bot+linux-riscv [this message]
2025-10-10  2:27   ` patchwork-bot+linux-riscv

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=176006323800.354358.6110592426551858799.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=justinstitt@google.com \
    --cc=leo.yan@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=llvm@lists.linux.dev \
    --cc=morbo@google.com \
    --cc=namhyung@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nick.desaulniers+lkml@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.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.