[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2d7c1890-9cd8-8134-af12-5c55cd7e1a8e@molgen.mpg.de>
Date: Fri, 3 Apr 2020 09:37:26 +0200
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: Aaron Ma <aaron.ma@...onical.com>,
Hans de Goede <hdegoede@...hat.com>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
davem@...emloft.net, intel-wired-lan@...ts.osuosl.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
sasha.neftin@...el.com
Subject: Re: [Intel-wired-lan] [PATCH] e1000e: bump up timeout to wait when ME
un-configure ULP mode
Dear Linux folks,
Am 03.04.20 um 05:15 schrieb Aaron Ma:
> I have received the email that you apply this patch to next-queue branch
> dev-queue.
>
> But after this branch is rebased to v5.6, I can't find it.
>
> Will you apply again?
I really urge you to write more elaborate commit messages.
The exact error is not listed. The known regressed devices are not
listed, so possible testers cannot easily test or affected people cannot
find it, when searching the Linux git history.
How did you find out, that ME takes more than two seconds?
Also, it’s not clear, what effect increasing the timeout has. Does the
whole resume process take longer or just getting the Ethernet device
back up?
Lastly, in case of the timeout, an error message should be printed, so
people with even more broken ME devices, get a clue.
Without this information, how can anybody know, if this is the right fix
and distributions, if it should be backported?
Kind regards,
Paul
Powered by blists - more mailing lists