From: Mark Brown <broonie@kernel.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Brian Norris <briannorris@chromium.org>,
Sean Paul <seanpaul@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <robert.foss@linaro.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
kernelci@lists.linux.dev
Subject: Re: renesas/master bisection: igt-kms-rockchip.kms_vblank.pipe-A-wait-forked on rk3399-gru-kevin
Date: Wed, 14 Dec 2022 13:50:16 +0000 [thread overview]
Message-ID: <Y5nUmJVmiOFfoMQl@sirena.org.uk> (raw)
In-Reply-To: <ea3d5e98-8901-1f9c-b27d-3c65e7969c41@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
On Wed, Dec 14, 2022 at 01:55:03PM +0100, Guillaume Tucker wrote:
> Maybe you could retrieve the original thread and rely to it with
> the report? That's the ideal way of following up on a patch I
> think. You can get the mbox file this way:
> ./kci_bisect get_mbox \
> --commit ca871659ec1606d33b1e76de8d4cf924cf627e34 \
> --kdir ~/src/linux
As a developer I tend to find this unhelpful, it makes it much more
likely that the mail will get missed. As a reporter it means there's
more information to copy into the report.
> > ... which is an old commit, added in v5.19-rc2, and which did not
> > enter through the renesas tree at all?
> Do you mean this report shouldn't have been sent to you?
I do notice that the Renesas tree tends to get a *lot* of the bisection
reports generated for some reason (vastly more than any other tree
including mainline or -next), however this wasn't sent based on the tree
at all - I just looked at the people involved with the commit.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Brian Norris <briannorris@chromium.org>,
Sean Paul <seanpaul@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <robert.foss@linaro.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
kernelci@lists.linux.dev
Subject: Re: renesas/master bisection: igt-kms-rockchip.kms_vblank.pipe-A-wait-forked on rk3399-gru-kevin
Date: Wed, 14 Dec 2022 13:50:16 +0000 [thread overview]
Message-ID: <Y5nUmJVmiOFfoMQl@sirena.org.uk> (raw)
In-Reply-To: <ea3d5e98-8901-1f9c-b27d-3c65e7969c41@collabora.com>
[-- Attachment #1.1: Type: text/plain, Size: 982 bytes --]
On Wed, Dec 14, 2022 at 01:55:03PM +0100, Guillaume Tucker wrote:
> Maybe you could retrieve the original thread and rely to it with
> the report? That's the ideal way of following up on a patch I
> think. You can get the mbox file this way:
> ./kci_bisect get_mbox \
> --commit ca871659ec1606d33b1e76de8d4cf924cf627e34 \
> --kdir ~/src/linux
As a developer I tend to find this unhelpful, it makes it much more
likely that the mail will get missed. As a reporter it means there's
more information to copy into the report.
> > ... which is an old commit, added in v5.19-rc2, and which did not
> > enter through the renesas tree at all?
> Do you mean this report shouldn't have been sent to you?
I do notice that the Renesas tree tends to get a *lot* of the bisection
reports generated for some reason (vastly more than any other tree
including mainline or -next), however this wasn't sent based on the tree
at all - I just looked at the people involved with the commit.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Mark Brown <broonie@kernel.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Jonas Karlman <jonas@kwiboo.se>,
Brian Norris <briannorris@chromium.org>,
Douglas Anderson <dianders@chromium.org>,
dri-devel@lists.freedesktop.org,
Sean Paul <seanpaul@chromium.org>,
Robert Foss <robert.foss@linaro.org>,
Andrzej Hajda <andrzej.hajda@intel.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
kernelci@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
Subject: Re: renesas/master bisection: igt-kms-rockchip.kms_vblank.pipe-A-wait-forked on rk3399-gru-kevin
Date: Wed, 14 Dec 2022 13:50:16 +0000 [thread overview]
Message-ID: <Y5nUmJVmiOFfoMQl@sirena.org.uk> (raw)
In-Reply-To: <ea3d5e98-8901-1f9c-b27d-3c65e7969c41@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 982 bytes --]
On Wed, Dec 14, 2022 at 01:55:03PM +0100, Guillaume Tucker wrote:
> Maybe you could retrieve the original thread and rely to it with
> the report? That's the ideal way of following up on a patch I
> think. You can get the mbox file this way:
> ./kci_bisect get_mbox \
> --commit ca871659ec1606d33b1e76de8d4cf924cf627e34 \
> --kdir ~/src/linux
As a developer I tend to find this unhelpful, it makes it much more
likely that the mail will get missed. As a reporter it means there's
more information to copy into the report.
> > ... which is an old commit, added in v5.19-rc2, and which did not
> > enter through the renesas tree at all?
> Do you mean this report shouldn't have been sent to you?
I do notice that the Renesas tree tends to get a *lot* of the bisection
reports generated for some reason (vastly more than any other tree
including mainline or -next), however this wasn't sent based on the tree
at all - I just looked at the people involved with the commit.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-12-14 13:50 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6398848e.170a0220.f8e8e.d44f@mx.google.com>
2022-12-13 16:51 ` renesas/master bisection: igt-kms-rockchip.kms_vblank.pipe-A-wait-forked on rk3399-gru-kevin Mark Brown
2022-12-13 16:51 ` Mark Brown
2022-12-14 10:06 ` Geert Uytterhoeven
2022-12-14 10:06 ` Geert Uytterhoeven
2022-12-14 12:55 ` Guillaume Tucker
2022-12-14 12:55 ` Guillaume Tucker
2022-12-14 12:55 ` Guillaume Tucker
2022-12-14 13:50 ` Mark Brown [this message]
2022-12-14 13:50 ` Mark Brown
2022-12-14 13:50 ` Mark Brown
2022-12-14 14:27 ` Guillaume Tucker
2022-12-14 14:27 ` Guillaume Tucker
2022-12-14 14:27 ` Guillaume Tucker
2022-12-14 14:54 ` Mark Brown
2022-12-14 14:54 ` Mark Brown
2022-12-14 14:54 ` Mark Brown
2022-12-14 14:03 ` Geert Uytterhoeven
2022-12-14 14:03 ` Geert Uytterhoeven
2022-12-14 14:03 ` Geert Uytterhoeven
2022-12-14 14:16 ` Guillaume Tucker
2022-12-14 14:16 ` Guillaume Tucker
2022-12-14 14:16 ` Guillaume Tucker
2022-12-14 14:39 ` Mark Brown
2022-12-14 14:39 ` Mark Brown
2022-12-14 14:39 ` Mark Brown
2022-12-14 15:02 ` Geert Uytterhoeven
2022-12-14 15:02 ` Geert Uytterhoeven
2022-12-14 15:02 ` Geert Uytterhoeven
2022-12-14 15:06 ` Geert Uytterhoeven
2022-12-14 15:06 ` Geert Uytterhoeven
2022-12-14 15:06 ` Geert Uytterhoeven
2022-12-15 3:04 ` Brian Norris
2022-12-15 3:04 ` Brian Norris
2022-12-21 22:02 ` Brian Norris
2022-12-21 22:02 ` Brian Norris
2023-01-03 18:04 ` Michel Dänzer
2023-01-03 18:04 ` Michel Dänzer
2023-01-04 2:11 ` Brian Norris
2023-01-04 2:11 ` Brian Norris
2023-01-04 9:11 ` Michel Dänzer
2023-01-04 9:11 ` Michel Dänzer
2023-01-06 0:59 ` Brian Norris
2023-01-06 0:59 ` Brian Norris
2023-01-06 1:43 ` Brian Norris
2023-01-06 1:43 ` Brian Norris
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=Y5nUmJVmiOFfoMQl@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=andrzej.hajda@intel.com \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=guillaume.tucker@collabora.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=kernelci@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=robert.foss@linaro.org \
--cc=seanpaul@chromium.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 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.