From: "Linux regression tracking #adding (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Alexander Stein <alexander.stein@ew.tq-group.com>,
linux-media@vger.kernel.org,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: v4l2-async: regression due to endpoint matching
Date: Mon, 26 Jun 2023 13:41:21 +0200 [thread overview]
Message-ID: <fa1fe0cc-4e87-78fb-fa89-3d0ac9d90bf3@leemhuis.info> (raw)
In-Reply-To: <aea6c4a7-5bb0-9395-8883-6b163c181995@leemhuis.info>
On 28.04.23 08:52, Linux regression tracking #adding (Thorsten Leemhuis)
wrote:
> [CCing the regression list, as it should be in the loop for regressions:
> https://docs.kernel.org/admin-guide/reporting-regressions.html]
>
> [TLDR: I'm adding this report to the list of tracked Linux kernel
> regressions; the text you find below is based on a few templates
> paragraphs you might have encountered already in similar form.
> See link in footer if these mails annoy you.]
>
> On 27.04.23 16:40, Alexander Stein wrote:
>>
>> I have a setup on my TQMa6x (imx6q-mba6a.dts) with a tc358743 attached to the
>> MIPI CSI input.
>> I noticed that since commit 1f391df44607 ("media: v4l2-async: Use endpoints in
>> __v4l2_async_nf_add_fwnode_remote()") the async subdevice probing does not
>> work anymore. If I revert that, it is working again, even on next-20230425.
>> [...]
>
> Thanks for the report. To be sure the issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
> tracking bot:
>
> #regzbot ^introduced 1f391df44607
> #regzbot title media: v4l2-async: async subdevice probing stopped
> working on TQMa6x
> #regzbot ignore-activity
I'm removing this from the list of tracked regressions, because as I
understand things a revert would cause a regressions itself; a quick fix
sadly is not really possible and a proper one already WIP[1]. There
hence is not much worth tracking this. Should happen in a ideal world,
but that's how it is sometimes:
#regzbot inconclusive: revert no option and a proper fix will take some time
#regzbot ignore-activity
[1] afaics it's this, but I might be wrong with
https://lore.kernel.org/all/20230622114028.908825-1-sakari.ailus@linux.intel.com/
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2023-06-26 11:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 14:40 v4l2-async: regression due to endpoint matching Alexander Stein
2023-04-27 16:01 ` Jacopo Mondi
2023-04-28 6:24 ` Alexander Stein
2023-04-28 6:31 ` Jacopo Mondi
2023-04-28 6:33 ` Alexander Stein
2023-04-28 6:43 ` Jacopo Mondi
2023-04-28 7:16 ` Sakari Ailus
2023-05-22 10:53 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 11:59 ` Sakari Ailus
2023-05-22 12:11 ` Linux regression tracking (Thorsten Leemhuis)
2023-05-22 12:51 ` Sakari Ailus
2023-05-24 11:52 ` Thorsten Leemhuis
2023-05-25 7:23 ` Sakari Ailus
2023-04-28 6:52 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-06-26 11:41 ` Linux regression tracking #adding (Thorsten Leemhuis) [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=fa1fe0cc-4e87-78fb-fa89-3d0ac9d90bf3@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=alexander.stein@ew.tq-group.com \
--cc=linux-media@vger.kernel.org \
--cc=regressions@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.