On Fri, Jun 14, 2019 at 06:10:20PM -0400, Lyude Paul wrote:
uh, Sasha not sure if you're a bot or not but this patch isn't even upstream
This is indeed a bot, and that's indeed it's purpose :)
We tend to get less responses if we wait for weeks for a patch to get
upstream and queued for
uh, Sasha not sure if you're a bot or not but this patch isn't even upstream
On Fri, 2019-06-14 at 21:56 +, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: all
The bot has tested the following trees: v5.1.9, v4.19.50, v4.14.125, v4.9.181,
v4.4.181.
v5.1.9: Build failed! Errors:
On Mon, 2018-11-26 at 21:53 +, Li, Juston wrote:
> Sorry for the late reply, email got caught in a bad filter =/
>
> I haven't been looking into it lately but we are still interested in
> getting this fixed so I can start looking into this again.
>
> In your last email you mentioned a sysfs
Sorry for the late reply, email got caught in a bad filter =/
I haven't been looking into it lately but we are still interested in
getting this fixed so I can start looking into this again.
In your last email you mentioned a sysfs hotplug could be the way to
go?
Thanks
Juston
On Thu,
Are you still looking into this at all? Even if it's not the right approach
I'm still interested in seeing this get fixed as well/discussing what I said
before
On Wed, 2018-10-24 at 22:45 +, Li, Juston wrote:
> On Wed, 2018-10-24 at 18:09 -0400, Lyude Paul wrote:
> > Since there's going to be
Gah, the more I think about this the more I realize this was never the correct
approach to begin with. I wrote this patch a long time ago when I wasn't
nearly as experienced, so that's not terribly surprising.
So: the thing is this isn't actually a problem that's specific to MST. Pretty
much all
On Wed, 2018-10-24 at 18:09 -0400, Lyude Paul wrote:
> Since there's going to be quite a number of changes I need to make to
> this I'm
> just going to make the changes myself! I'll make sure to Cc you with
> the
> respin
Sounds good, thanks for picking it up!
Juston
Thought this was going to be an easy review until I realized that there's
multiple problems in nouveau this would cause issues with, even if we didn't
pay attention to the -EINVAL that gets returned. The suspend/resume order in
nouveau needs some fixing up to prevent this patch from causing
From: Lyude
As observed with the latest ThinkPad docks, we unfortunately can't rely
on docks keeping us updated with hotplug events that happened while we
were suspended. On top of that, even if the number of connectors remains
the same between suspend and resume it's still not safe to assume
10 matches
Mail list logo
