Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Valentin Obst <kernel@valentinobst.de>
Cc: anders.roxell@linaro.org, bpoirier@nvidia.com,
	broonie@kernel.org, guillaume.tucker@collabora.com,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	mpdesouza@suse.com, nathan@kernel.org, sashal@kernel.org,
	shuah@kernel.org
Subject: Re: [PATCH] selftests: default to host arch for LLVM builds
Date: Sun, 28 Apr 2024 15:04:42 -0700	[thread overview]
Message-ID: <b728014e-9e8f-4b65-8d9e-ace0e2f6f18c@nvidia.com> (raw)
In-Reply-To: <20240428120806.19275-1-kernel@valentinobst.de>

On 4/28/24 5:08 AM, Valentin Obst wrote:
...
>> And yes, the selftests "normal" (non-cross-compile) build is *broken*
>> right now, for clang. I didn't realize from the patch title that this is
>> actually a significant fix. Maybe we should change the subject line (patch
>> title) to something like:
>>
>>      [PATCH] selftests: fix the clang build: default to host arch for LLVM builds
> 
> Yes, I agree that the title should contain the word 'fix' somewhere. For
> me its okay if maintainers reword the title when applying the patch,
> alternatively I can send a v2. (Is it still a v2 if I change the title, or
> rather a new patch?).

It would still be a v2, although the cover letter, or the section after the
"---", would need to point to v1 so that people could make the connection.

> 
> Any thoughts on whether this also needs a 'Cc stable'? Its not quite
> clear to me if this fix meets the requirements. As above, no objections if
> maintainers should decide to add it.
> 

Maybe not, because it doesn't seem urgent. But it's a judgment call.

By the way, I've been chipping away at fixing clang selftest build
failures and warnings that are only visible after clang is working again
(due to your fix here), and I'm up to 30+ patches, and probably only a
few more to go to get all of them.

I'm expecting to post the series soon, hopefully this week. And I'm
thinking maybe I should carry your patch as the first one in the series,
in order to ensure it gets picked up. Or, I can just refer to it as a
prerequisite in the cover letter.


thanks,
-- 
John Hubbard
NVIDIA


  reply	other threads:[~2024-04-28 22:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-29 10:49 [PATCH] selftests: default to host arch for LLVM builds Valentin Obst
2024-04-13 22:10 ` John Hubbard
2024-04-28 12:08   ` Valentin Obst
2024-04-28 22:04     ` John Hubbard [this message]
2024-04-30 11:44       ` Valentin Obst
2024-04-30 14:50         ` Mark Brown
2024-04-30 16:58           ` John Hubbard
2024-05-03 19:55     ` Shuah Khan

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=b728014e-9e8f-4b65-8d9e-ace0e2f6f18c@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=anders.roxell@linaro.org \
    --cc=bpoirier@nvidia.com \
    --cc=broonie@kernel.org \
    --cc=guillaume.tucker@collabora.com \
    --cc=kernel@valentinobst.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mpdesouza@suse.com \
    --cc=nathan@kernel.org \
    --cc=sashal@kernel.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