From: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>
To: Mark Brown <broonie@kernel.org>
Cc: Guillaume Tucker <guillaume.tucker@collabora.com>,
kernelci@lists.linux.dev
Subject: Re: Reduced build and test coverage
Date: Tue, 19 Sep 2023 16:44:06 +0200 [thread overview]
Message-ID: <87ediudxzd.fsf@collabora.com> (raw)
In-Reply-To: <8840c525-4e80-48dd-a31f-40f2ca4ed03e@sirena.org.uk>
On mar, sep 19 2023 at 15:31:31, Mark Brown <broonie@kernel.org> wrote:
> If we're doing this -next would be very helpful too.
Does it make sense to bisect -next, though? Considering that it's
constantly rebased, so I don't think it has a coherent and "linear" log
like mainline. That means that bisections aren't guaranteed to work on
it. Is that right?
Ricardo
next prev parent reply other threads:[~2023-09-19 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 13:51 Reduced build and test coverage Guillaume Tucker
2023-07-13 5:51 ` Guillaume Tucker
2023-09-19 14:29 ` Ricardo Cañuelo
2023-09-19 14:31 ` Mark Brown
2023-09-19 14:44 ` Ricardo Cañuelo [this message]
2023-09-19 16:12 ` Mark Brown
2023-09-19 16:43 ` Guillaume Charles Tucker
2023-09-25 8:50 ` Guillaume Tucker
2023-10-10 10:43 ` Guillaume Tucker
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=87ediudxzd.fsf@collabora.com \
--to=ricardo.canuelo@collabora.com \
--cc=broonie@kernel.org \
--cc=guillaume.tucker@collabora.com \
--cc=kernelci@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).