From: Palmer Dabbelt <palmer@rivosinc.com>
To: Andrew Morton <akpm@linux-foundation.org>,
John Hubbard <jhubbard@nvidia.com>
Cc: Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alexghiti@rivosinc.com>,
Anders Roxell <anders.roxell@linaro.org>,
Andrew Jones <ajones@ventanamicro.com>,
Andy Chiu <andy.chiu@sifive.com>, Evan Green <evan@rivosinc.com>,
Hugh Dickins <hughd@google.com>,
Muhammad Usama Anjum <usama.anjum@collabora.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Qinglin Pan <panqinglin2020@iscas.ac.cn>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] selftests/riscv: fix potential build failure during the "emit_tests" step
Date: Thu, 03 Aug 2023 07:45:24 -0700 [thread overview]
Message-ID: <169107392499.27633.6579477595845776477.b4-ty@rivosinc.com> (raw)
In-Reply-To: <20230712193514.740033-1-jhubbard@nvidia.com>
On Wed, 12 Jul 2023 12:35:14 -0700, John Hubbard 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.
>
> [...]
Applied, thanks!
[1/1] selftests/riscv: fix potential build failure during the "emit_tests" step
https://git.kernel.org/palmer/c/8c82d2bf5944
Best regards,
--
Palmer Dabbelt <palmer@rivosinc.com>
next prev parent reply other threads:[~2023-08-03 15:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 19:35 John Hubbard
2023-07-13 11:51 ` Alexandre Ghiti
2023-08-03 14:45 ` Palmer Dabbelt [this message]
2023-08-03 16:48 ` Shuah Khan
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=169107392499.27633.6579477595845776477.b4-ty@rivosinc.com \
--to=palmer@rivosinc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox