All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-riscv@kernel.org
To: John Hubbard <jhubbard@nvidia.com>
Cc: linux-riscv@lists.infradead.org, akpm@linux-foundation.org,
	aou@eecs.berkeley.edu, alexghiti@rivosinc.com,
	anders.roxell@linaro.org, ajones@ventanamicro.com,
	andy.chiu@sifive.com, evan@rivosinc.com, hughd@google.com,
	usama.anjum@collabora.com, palmer@dabbelt.com,
	paul.walmsley@sifive.com, panqinglin2020@iscas.ac.cn,
	shuah@kernel.org, linux-kselftest@vger.kernel.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/riscv: fix potential build failure during the "emit_tests" step
Date: Thu, 03 Aug 2023 15:10:23 +0000	[thread overview]
Message-ID: <169107542311.19238.11249347839219210996.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230712193514.740033-1-jhubbard@nvidia.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed, 12 Jul 2023 12:35:14 -0700 you wrote:
> The riscv selftests (which were modeled after the arm64 selftests) are
> improperly declaring the "emit_tests" target to depend upon the "all"
> target. This approach, when combined with commit 9fc96c7c19df
> ("selftests: error out if kernel header files are not yet built"), has
> caused build failures [1] on arm64, and is likely to cause similar
> failures for riscv.
> 
> [...]

Here is the summary with links:
  - selftests/riscv: fix potential build failure during the "emit_tests" step
    https://git.kernel.org/riscv/c/8c82d2bf5944

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: John Hubbard <jhubbard@nvidia.com>
Cc: linux-riscv@lists.infradead.org, akpm@linux-foundation.org,
	aou@eecs.berkeley.edu, alexghiti@rivosinc.com,
	anders.roxell@linaro.org, ajones@ventanamicro.com,
	andy.chiu@sifive.com, evan@rivosinc.com, hughd@google.com,
	usama.anjum@collabora.com, palmer@dabbelt.com,
	paul.walmsley@sifive.com, panqinglin2020@iscas.ac.cn,
	shuah@kernel.org, linux-kselftest@vger.kernel.org,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/riscv: fix potential build failure during the "emit_tests" step
Date: Thu, 03 Aug 2023 15:10:23 +0000	[thread overview]
Message-ID: <169107542311.19238.11249347839219210996.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230712193514.740033-1-jhubbard@nvidia.com>

Hello:

This patch was applied to riscv/linux.git (fixes)
by Palmer Dabbelt <palmer@rivosinc.com>:

On Wed, 12 Jul 2023 12:35:14 -0700 you wrote:
> The riscv selftests (which were modeled after the arm64 selftests) are
> improperly declaring the "emit_tests" target to depend upon the "all"
> target. This approach, when combined with commit 9fc96c7c19df
> ("selftests: error out if kernel header files are not yet built"), has
> caused build failures [1] on arm64, and is likely to cause similar
> failures for riscv.
> 
> [...]

Here is the summary with links:
  - selftests/riscv: fix potential build failure during the "emit_tests" step
    https://git.kernel.org/riscv/c/8c82d2bf5944

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:[~2023-08-03 15:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 19:35 [PATCH] selftests/riscv: fix potential build failure during the "emit_tests" step John Hubbard
2023-07-12 19:35 ` John Hubbard
2023-07-13 11:51 ` Alexandre Ghiti
2023-07-13 11:51   ` Alexandre Ghiti
2023-08-03 14:45 ` Palmer Dabbelt
2023-08-03 14:45   ` Palmer Dabbelt
2023-08-03 16:48   ` Shuah Khan
2023-08-03 16:48     ` Shuah Khan
2023-08-03 15:10 ` patchwork-bot+linux-riscv [this message]
2023-08-03 15:10   ` 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=169107542311.19238.11249347839219210996.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-riscv@kernel.org \
    --cc=ajones@ventanamicro.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexghiti@rivosinc.com \
    --cc=anders.roxell@linaro.org \
    --cc=andy.chiu@sifive.com \
    --cc=aou@eecs.berkeley.edu \
    --cc=evan@rivosinc.com \
    --cc=hughd@google.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=palmer@dabbelt.com \
    --cc=panqinglin2020@iscas.ac.cn \
    --cc=paul.walmsley@sifive.com \
    --cc=shuah@kernel.org \
    --cc=usama.anjum@collabora.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.