From: Guillaume Tucker <guillaume.tucker@collabora.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Shuah Khan <shuah@kernel.org>, Borislav Petkov <bp@suse.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
kernel@collabora.com, linux-mm@kvack.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests, x86: fix how check_cc.sh is being invoked
Date: Fri, 11 Mar 2022 10:15:20 +0000 [thread overview]
Message-ID: <89e684cb-8cac-541b-10f0-39a6ba1089d3@collabora.com> (raw)
In-Reply-To: <20220225170305.de0aa0dc898ca583d8a83e5c@linux-foundation.org>
On 26/02/2022 01:03, Andrew Morton wrote:
> On Fri, 25 Feb 2022 13:15:43 +0000 Guillaume Tucker <guillaume.tucker@collabora.com> wrote:
>
>> Add quotes around $(CC) when calling check_cc.sh from a Makefile to
>> pass the value as a single argument to the script even if it has
>> several words such as "ccache gcc". Conversely, remove quotes in
>> check_cc.sh when calling $CC to make it a command with potentially
>> several arguments again.
>
> This changelog describes the fix, but it fails to describe the problem
> which the patch is fixing!
>
> Presumably, we're hitting some form of runtime failure under
> undescribed circumstances when running selftests. But that's just me
> reverse-engineering the patch description. And me reverse-engineering
> stuff is a gloriously unreliable thing. Please spell out the problem.
Thanks for the review. I've just sent a v2 which is rebased on
other changes in linux-next and with a reworked commit message
which should hopefully be clearer. The issue was seen when
building some kselftest binaries and $CC is defined with multiple
arguments such as "ccache gcc".
Guillaume
prev parent reply other threads:[~2022-03-11 10:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 13:15 Guillaume Tucker
2022-02-25 18:49 ` Guillaume Tucker
2022-02-25 21:38 ` David Laight
2022-02-26 1:03 ` Andrew Morton
2022-03-11 10:15 ` Guillaume Tucker [this message]
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=89e684cb-8cac-541b-10f0-39a6ba1089d3@collabora.com \
--to=guillaume.tucker@collabora.com \
--cc=akpm@linux-foundation.org \
--cc=bp@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shuah@kernel.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