From: Andrew Lunn <andrew@lunn.ch>
To: En-Wei WU <en-wei.wu@canonical.com>
Cc: Sasha Neftin <sasha.neftin@intel.com>,
anthony.l.nguyen@intel.com, netdev@vger.kernel.org,
rickywu0421@gmail.com, linux-kernel@vger.kernel.org,
edumazet@google.com, pabeni@redhat.com,
intel-wired-lan@lists.osuosl.org, "Lifshits,
Vitaly" <vitaly.lifshits@intel.com>,
kuba@kernel.org, "Ruinskiy, Dima" <dima.ruinskiy@intel.com>,
davem@davemloft.net
Subject: Re: [Intel-wired-lan] [PATCH v2 1/2] e1000e: let the sleep codes run every time
Date: Tue, 7 May 2024 14:29:25 +0200 [thread overview]
Message-ID: <010c2d24-201e-4aba-b4a1-d973545121a7@lunn.ch> (raw)
In-Reply-To: <CAMqyJG2S4yvO-UiCiWydO+9uzOWpeKR9tmMDWrw=m6O7pd3m0w@mail.gmail.com>
> > (1) How serious this problem is. It is normal for link establishment to
> > take a few seconds from plugging the cable (due to PHY
> > auto-negotiation), and I can accept some link instability during that time.
> Actually, the problem is not critical since the link will be up
> permanently after the unstable up-down problem when hot-plugging. And
> it has no functional impact on the system. But this problem can lead
> to a failure in our script (for Canonical Certification), and it's not
> tolerable.
Please could you describe your test. We should be sure you are fixing
the right thing. Maybe the test is broken, not the driver...
Andrew
prev parent reply other threads:[~2024-05-07 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 10:18 [Intel-wired-lan] [PATCH v2 1/2] e1000e: let the sleep codes run every time Ricky Wu
2024-05-03 18:17 ` Keller, Jacob E
2024-05-06 15:53 ` Sasha Neftin
2024-05-06 16:46 ` En-Wei WU
2024-05-07 6:21 ` Ruinskiy, Dima
2024-05-07 8:54 ` En-Wei WU
2024-05-07 12:29 ` Andrew Lunn [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=010c2d24-201e-4aba-b4a1-d973545121a7@lunn.ch \
--to=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=dima.ruinskiy@intel.com \
--cc=edumazet@google.com \
--cc=en-wei.wu@canonical.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rickywu0421@gmail.com \
--cc=sasha.neftin@intel.com \
--cc=vitaly.lifshits@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).