All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: =?utf-8?q?Christoph_M=C3=BCllner_=3Cchristoph=2Emuellner=40vrull=2Eeu=3E?=@ci.codeaurora.org
Cc: linux-riscv@lists.infradead.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org, palmer@dabbelt.com,
	paul.walmsley@sifive.com, aou@eecs.berkeley.edu,
	shuah@kernel.org, philipp.tomsich@vrull.eu,
	ajones@ventanamicro.com, evan@rivosinc.com,
	xiao.w.wang@intel.com, alexghiti@rivosinc.com,
	andy.chiu@sifive.com, bjorn@rivosinc.com, charlie@rivosinc.com
Subject: Re: [PATCH 0/5] tools: selftests: riscv: Fix compiler warnings
Date: Fri, 12 Jan 2024 06:30:30 +0000	[thread overview]
Message-ID: <170504103079.17535.4478051835218795004.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231123185821.2272504-1-christoph.muellner@vrull.eu>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Thu, 23 Nov 2023 19:58:16 +0100 you wrote:
> From: Christoph Müllner <christoph.muellner@vrull.eu>
> 
> When building the RISC-V selftests with a riscv32 compiler I ran into
> a couple of compiler warnings. While riscv32 support for these tests is
> questionable, the fixes are so trivial that it is probably best to simply
> apply them.
> 
> [...]

Here is the summary with links:
  - [1/5] tools: selftests: riscv: Fix compile warnings in hwprobe
    https://git.kernel.org/riscv/c/b91c26fdb0e8
  - [2/5] tools: selftests: riscv: Fix compile warnings in cbo
    https://git.kernel.org/riscv/c/ac7b2a02d62f
  - [3/5] tools: selftests: riscv: Add missing include for vector test
    https://git.kernel.org/riscv/c/b250c9089841
  - [4/5] tools: selftests: riscv: Fix compile warnings in vector tests
    https://git.kernel.org/riscv/c/e1baf5e68ed1
  - [5/5] tools: selftests: riscv: Fix compile warnings in mm tests
    https://git.kernel.org/riscv/c/12c16919652b

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: =?utf-8?q?Christoph_M=C3=BCllner_=3Cchristoph=2Emuellner=40vrull=2Eeu=3E?=@ci.codeaurora.org
Cc: linux-riscv@lists.infradead.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org, palmer@dabbelt.com,
	paul.walmsley@sifive.com, aou@eecs.berkeley.edu,
	shuah@kernel.org, philipp.tomsich@vrull.eu,
	ajones@ventanamicro.com, evan@rivosinc.com,
	xiao.w.wang@intel.com, alexghiti@rivosinc.com,
	andy.chiu@sifive.com, bjorn@rivosinc.com, charlie@rivosinc.com
Subject: Re: [PATCH 0/5] tools: selftests: riscv: Fix compiler warnings
Date: Fri, 12 Jan 2024 06:30:30 +0000	[thread overview]
Message-ID: <170504103079.17535.4478051835218795004.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231123185821.2272504-1-christoph.muellner@vrull.eu>

Hello:

This series was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Thu, 23 Nov 2023 19:58:16 +0100 you wrote:
> From: Christoph Müllner <christoph.muellner@vrull.eu>
> 
> When building the RISC-V selftests with a riscv32 compiler I ran into
> a couple of compiler warnings. While riscv32 support for these tests is
> questionable, the fixes are so trivial that it is probably best to simply
> apply them.
> 
> [...]

Here is the summary with links:
  - [1/5] tools: selftests: riscv: Fix compile warnings in hwprobe
    https://git.kernel.org/riscv/c/b91c26fdb0e8
  - [2/5] tools: selftests: riscv: Fix compile warnings in cbo
    https://git.kernel.org/riscv/c/ac7b2a02d62f
  - [3/5] tools: selftests: riscv: Add missing include for vector test
    https://git.kernel.org/riscv/c/b250c9089841
  - [4/5] tools: selftests: riscv: Fix compile warnings in vector tests
    https://git.kernel.org/riscv/c/e1baf5e68ed1
  - [5/5] tools: selftests: riscv: Fix compile warnings in mm tests
    https://git.kernel.org/riscv/c/12c16919652b

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:[~2024-01-12  6:30 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23 18:58 [PATCH 0/5] tools: selftests: riscv: Fix compiler warnings Christoph Muellner
2023-11-23 18:58 ` Christoph Muellner
2023-11-23 18:58 ` [PATCH 1/5] tools: selftests: riscv: Fix compile warnings in hwprobe Christoph Muellner
2023-11-23 18:58   ` Christoph Muellner
2023-12-15 13:41   ` Alexandre Ghiti
2023-12-15 13:41     ` Alexandre Ghiti
2023-12-15 13:52   ` Alexandre Ghiti
2023-12-15 13:52     ` Alexandre Ghiti
2023-11-23 18:58 ` [PATCH 2/5] tools: selftests: riscv: Fix compile warnings in cbo Christoph Muellner
2023-11-23 18:58   ` Christoph Muellner
2023-12-15 13:54   ` Alexandre Ghiti
2023-12-15 13:54     ` Alexandre Ghiti
2023-11-23 18:58 ` [PATCH 3/5] tools: selftests: riscv: Add missing include for vector test Christoph Muellner
2023-11-23 18:58   ` Christoph Muellner
2023-12-15 13:57   ` Alexandre Ghiti
2023-12-15 13:57     ` Alexandre Ghiti
2023-12-15 15:38   ` Andy Chiu
2023-12-15 15:38     ` Andy Chiu
2023-11-23 18:58 ` [PATCH 4/5] tools: selftests: riscv: Fix compile warnings in vector tests Christoph Muellner
2023-11-23 18:58   ` Christoph Muellner
2023-12-15 13:44   ` Alexandre Ghiti
2023-12-15 13:44     ` Alexandre Ghiti
2023-11-23 18:58 ` [PATCH 5/5] tools: selftests: riscv: Fix compile warnings in mm tests Christoph Muellner
2023-11-23 18:58   ` Christoph Muellner
2023-12-15 13:50   ` Alexandre Ghiti
2023-12-15 13:50     ` Alexandre Ghiti
2023-11-24  9:40 ` [PATCH 0/5] tools: selftests: riscv: Fix compiler warnings Andrew Jones
2023-11-24  9:40   ` Andrew Jones
2023-12-15 10:02   ` Christoph Müllner
2023-12-15 10:02     ` Christoph Müllner
2024-01-12  6:30 ` patchwork-bot+linux-riscv [this message]
2024-01-12  6:30   ` 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=170504103079.17535.4478051835218795004.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc==?utf-8?q?Christoph_M=C3=BCllner_=3Cchristoph=2Emuellner=40vrull=2Eeu=3E?=@ci.codeaurora.org \
    --cc=ajones@ventanamicro.com \
    --cc=alexghiti@rivosinc.com \
    --cc=andy.chiu@sifive.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=bjorn@rivosinc.com \
    --cc=charlie@rivosinc.com \
    --cc=evan@rivosinc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=shuah@kernel.org \
    --cc=xiao.w.wang@intel.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.