From: Guenter Roeck <linux@roeck-us.net>
To: "Limonciello, Mario" <Mario.Limonciello@amd.com>
Cc: "Lin, Wayne" <Wayne.Lin@amd.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"stanislav.lisovskiy@intel.com" <stanislav.lisovskiy@intel.com>,
"Zuo, Jerry" <Jerry.Zuo@amd.com>,
"bskeggs@redhat.com" <bskeggs@redhat.com>
Subject: Re: [PATCH] Revert "drm/display/dp_mst: Move all payload info into the atomic state"
Date: Fri, 20 Jan 2023 13:00:40 -0800 [thread overview]
Message-ID: <9927d839-4abc-0daf-36cd-e547beb7c87d@roeck-us.net> (raw)
In-Reply-To: <MN0PR12MB6101FE67D355FF2A47470C37E2C59@MN0PR12MB6101.namprd12.prod.outlook.com>
On 1/20/23 10:39, Limonciello, Mario wrote:
[ ... ]
>>>
>>> Wayne is OOO for CNY, but let me update you.
>>>
>>> Harry has sent out this series which is a collection of proper fixes.
>>> https://patchwork.freedesktop.org/series/113125/
>>>
>>> Once that's reviewed and accepted, 4 of them are applicable for 6.1.
>>
>> Thanks a lot for the update. There is talk about abandoning v6.1.y as
>> LTS candidate, in large part due to this problem, so it would be great
>> to get the problem fixed before that happens.
>
> Any idea how soon that decision is happening? It seems that we have line
> of sight to a solution including back to 6.1.y pending that review. So perhaps
> we can put off the decision until those are landed.
I honestly don't know. All I know is that Greg is concerned about
the number of regressions in v6.1.y, and this problem was one
he specifically mentioned to me as potential reason to not designate
6.1.y as LTS kernel. The extensive discussion at [1] may be an
indication that there is a problem, though that mostly refers to
[lack of] test coverage and does not point to specific regressions.
Guenter
---
[1] https://lore.kernel.org/lkml/CAPDLWs-Z8pYkwQ13dEgHXqSCjiq4xVnjuAXTy26H3=8NZCpV_g@mail.gmail.com/
WARNING: multiple messages have this Message-ID (diff)
From: Guenter Roeck <linux@roeck-us.net>
To: "Limonciello, Mario" <Mario.Limonciello@amd.com>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"stanislav.lisovskiy@intel.com" <stanislav.lisovskiy@intel.com>,
"Zuo, Jerry" <Jerry.Zuo@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Lin, Wayne" <Wayne.Lin@amd.com>,
"bskeggs@redhat.com" <bskeggs@redhat.com>
Subject: Re: [PATCH] Revert "drm/display/dp_mst: Move all payload info into the atomic state"
Date: Fri, 20 Jan 2023 13:00:40 -0800 [thread overview]
Message-ID: <9927d839-4abc-0daf-36cd-e547beb7c87d@roeck-us.net> (raw)
In-Reply-To: <MN0PR12MB6101FE67D355FF2A47470C37E2C59@MN0PR12MB6101.namprd12.prod.outlook.com>
On 1/20/23 10:39, Limonciello, Mario wrote:
[ ... ]
>>>
>>> Wayne is OOO for CNY, but let me update you.
>>>
>>> Harry has sent out this series which is a collection of proper fixes.
>>> https://patchwork.freedesktop.org/series/113125/
>>>
>>> Once that's reviewed and accepted, 4 of them are applicable for 6.1.
>>
>> Thanks a lot for the update. There is talk about abandoning v6.1.y as
>> LTS candidate, in large part due to this problem, so it would be great
>> to get the problem fixed before that happens.
>
> Any idea how soon that decision is happening? It seems that we have line
> of sight to a solution including back to 6.1.y pending that review. So perhaps
> we can put off the decision until those are landed.
I honestly don't know. All I know is that Greg is concerned about
the number of regressions in v6.1.y, and this problem was one
he specifically mentioned to me as potential reason to not designate
6.1.y as LTS kernel. The extensive discussion at [1] may be an
indication that there is a problem, though that mostly refers to
[lack of] test coverage and does not point to specific regressions.
Guenter
---
[1] https://lore.kernel.org/lkml/CAPDLWs-Z8pYkwQ13dEgHXqSCjiq4xVnjuAXTy26H3=8NZCpV_g@mail.gmail.com/
next prev parent reply other threads:[~2023-01-20 21:00 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 8:50 [PATCH] Revert "drm/display/dp_mst: Move all payload info into the atomic state" Wayne Lin
2023-01-12 8:50 ` Wayne Lin
2023-01-12 8:50 ` Wayne Lin
2023-01-12 17:37 ` Limonciello, Mario
2023-01-12 17:37 ` Limonciello, Mario
2023-01-12 17:37 ` Limonciello, Mario
2023-01-12 21:16 ` Lyude Paul
2023-01-12 21:16 ` Lyude Paul
2023-01-12 21:16 ` Lyude Paul
2023-01-13 10:16 ` Jani Nikula
2023-01-13 10:16 ` Jani Nikula
2023-01-13 10:16 ` [Intel-gfx] " Jani Nikula
2023-01-13 10:25 ` Daniel Vetter
2023-01-13 10:25 ` Daniel Vetter
2023-01-13 10:25 ` Daniel Vetter
2023-01-13 10:25 ` [Intel-gfx] " Daniel Vetter
2023-01-13 16:19 ` Harry Wentland
2023-01-13 16:19 ` Harry Wentland
2023-01-13 16:19 ` [Intel-gfx] " Harry Wentland
2023-01-13 19:28 ` Lyude Paul
2023-01-13 19:28 ` Lyude Paul
2023-01-13 19:28 ` Lyude Paul
2023-01-13 19:28 ` [Intel-gfx] " Lyude Paul
2023-01-13 19:45 ` Limonciello, Mario
2023-01-13 19:45 ` Limonciello, Mario
2023-01-13 19:45 ` Limonciello, Mario
2023-01-13 19:45 ` [Intel-gfx] " Limonciello, Mario
2023-01-20 17:46 ` Guenter Roeck
2023-01-20 17:46 ` Guenter Roeck
2023-01-20 17:51 ` Limonciello, Mario
2023-01-20 17:51 ` Limonciello, Mario
2023-01-20 18:18 ` Guenter Roeck
2023-01-20 18:18 ` Guenter Roeck
2023-01-20 18:39 ` Limonciello, Mario
2023-01-20 18:39 ` Limonciello, Mario
2023-01-20 21:00 ` Guenter Roeck [this message]
2023-01-20 21:00 ` Guenter Roeck
2023-01-27 7:39 ` Greg KH
2023-01-27 7:39 ` Greg KH
2023-01-27 9:15 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-27 9:15 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-27 15:02 ` Limonciello, Mario
2023-01-27 15:02 ` Limonciello, Mario
2023-01-29 13:31 ` Greg KH
2023-02-01 19:43 ` Limonciello, Mario
2023-01-27 14:24 ` Hamza Mahfooz
2023-01-27 14:24 ` Hamza Mahfooz
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=9927d839-4abc-0daf-36cd-e547beb7c87d@roeck-us.net \
--to=linux@roeck-us.net \
--cc=Jerry.Zuo@amd.com \
--cc=Mario.Limonciello@amd.com \
--cc=Wayne.Lin@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=stable@vger.kernel.org \
--cc=stanislav.lisovskiy@intel.com \
/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.