Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Mark Brown <broonie@kernel.org>, Valentin Obst <kernel@valentinobst.de>
Cc: anders.roxell@linaro.org, bpoirier@nvidia.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: Tue, 30 Apr 2024 09:58:00 -0700	[thread overview]
Message-ID: <e008af14-7222-4796-91d3-d04af463bf40@nvidia.com> (raw)
In-Reply-To: <ZjEFOj8NXGO72Ocl@finisterre.sirena.org.uk>

On 4/30/24 7:50 AM, Mark Brown wrote:
> On Tue, Apr 30, 2024 at 01:44:52PM +0200, Valentin Obst wrote:
>> On 4/29/24 12:04 AM, John Hubbard wrote:
>> Correct me if I'm wrong, but intuitively 30+ patches that touch selftests
>> from many different subsystems do not sound like something that is going
>> to be merged fast. Since I'm also planning to send a separate series that
> 
> It just seems unhelpful to lump everything into a single series - a
> large portion of the selftests go with the subystems so you'd be
> creating a bunch of cross subsystem issues and large serieses with big
> CC lists tend to be both offputting and noisy.

Thanks for this timely advice! I was on the fence about the best way to
send these out. I'll break it up into subsystem patchsets (that don't
directly include Valentin's patch, but do refer to it) instead, which as
you say, should go *much* more smoothly.

In fact, just yesterday I fixed the last warning, so I'll start posting
some much smaller patchsets later today.


thanks,
-- 
John Hubbard
NVIDIA


  reply	other threads:[~2024-04-30 16:58 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
2024-04-30 11:44       ` Valentin Obst
2024-04-30 14:50         ` Mark Brown
2024-04-30 16:58           ` John Hubbard [this message]
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=e008af14-7222-4796-91d3-d04af463bf40@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=anders.roxell@linaro.org \
    --cc=bpoirier@nvidia.com \
    --cc=broonie@kernel.org \
    --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