From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Mark Brown <broonie@kernel.org>
Cc: Andrew Lunn <andrew@lunn.ch>, Jiri Kosina <jikos@kernel.org>,
ksummit@lists.linux.dev, sashiko@lists.linux.dev
Subject: Re: Patch pre-submission to Sashiko
Date: Sun, 18 Oct 2026 18:48:05 +0200 [thread overview]
Message-ID: <20261018164805.GA664365@killaraus.ideasonboard.com> (raw)
In-Reply-To: <atSzd4EdU4_B5eKr@sirena.org.uk>
On Sun, Oct 18, 2026 at 12:54:31PM +0100, Mark Brown wrote:
> On Sat, Oct 17, 2026 at 09:42:34PM +0200, Andrew Lunn wrote:
> > On Sat, Oct 17, 2026 at 07:28:48PM +0200, Jiri Kosina wrote:
> >
> > > I have just received a v1 to v11 patchset submission within roughly one
> > > day timeframe.
> >
> > If they are iterating that fast, they either have automated tests, or
> > the code is untested. I would ask them to includes the tests in the
> > patchset, to become part of tools/testing/selftests.
>
> There's some work (init paths for drivers for example) where it's
> perfectly plausible that you can reverify things fast enough to be doing
> that. It's probably a relatively long day, but it's doable. You're
> more likely to hit numbers like that over a weekend though.
And let's not forget that for most patches touching drivers selftests
are not an option.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2026-10-18 16:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 17:28 Patch pre-submission to Sashiko Jiri Kosina
2026-10-17 18:02 ` Theodore Tso
2026-10-17 18:20 ` Alexei Starovoitov
2026-10-17 18:38 ` Arnaldo Melo
2026-10-18 11:46 ` Mark Brown
2026-10-17 18:20 ` Linus Torvalds
2026-10-17 20:10 ` Roman Gushchin
2026-10-18 13:41 ` Steven Rostedt
2026-10-18 18:41 ` Kees Cook
2026-10-18 18:58 ` Linus Torvalds
2026-10-17 19:42 ` Andrew Lunn
2026-10-18 11:54 ` Mark Brown
2026-10-18 16:48 ` Laurent Pinchart [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=20261018164805.GA664365@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=jikos@kernel.org \
--cc=ksummit@lists.linux.dev \
--cc=sashiko@lists.linux.dev \
/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.