diff for duplicates of <20200924160447.GD3821492@lunn.ch> diff --git a/a/1.txt b/N1/1.txt index 1e95056..4e42db0 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -7,7 +7,7 @@ On Thu, Sep 24, 2020 at 05:32:12PM +0200, Paul Menzel wrote: > Am 24.09.20 um 17:09 schrieb Kai-Heng Feng: > > We are seeing the following error after S3 resume: > -> I?d be great if you added the system and used hardware, you are seeing this +> I’d be great if you added the system and used hardware, you are seeing this > with. > > > [ 704.746874] e1000e 0000:00:1f.6 eno1: Setting page 0x6020 @@ -15,10 +15,10 @@ On Thu, Sep 24, 2020 at 05:32:12PM +0200, Paul Menzel wrote: > > A follow-up patch, should extend the message to include the timeout value. > -> > MDI Write did not complete did not complete in ? seconds. +> > MDI Write did not complete did not complete in … seconds. > -> According to the Linux timestamps it?s 98 ms, which makes sense, as (640 * 3 -> * 50 ?s = 96 ms). +> According to the Linux timestamps it’s 98 ms, which makes sense, as (640 * 3 +> * 50 μs = 96 ms). > > What crappy hardware is this, that it takes longer than 100 ms? diff --git a/a/content_digest b/N1/content_digest index 5605552..d16d244 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,9 +2,16 @@ "ref\020200924150958.18016-1-kai.heng.feng@canonical.com\0" "ref\0748efbf9-573f-ab2a-0c82-a7b2a11cda60@molgen.mpg.de\0" "From\0Andrew Lunn <andrew@lunn.ch>\0" - "Subject\0[Intel-wired-lan] [PATCH v2] e1000e: Increase iteration on polling MDIC ready bit\0" + "Subject\0Re: [Intel-wired-lan] [PATCH v2] e1000e: Increase iteration on polling MDIC ready bit\0" "Date\0Thu, 24 Sep 2020 18:04:47 +0200\0" - "To\0intel-wired-lan@osuosl.org\0" + "To\0Paul Menzel <pmenzel@molgen.mpg.de>\0" + "Cc\0Kai-Heng Feng <kai.heng.feng@canonical.com>" + Jeff Kirsher <jeffrey.t.kirsher@intel.com> + netdev@vger.kernel.org + linux-kernel@vger.kernel.org + intel-wired-lan@lists.osuosl.org + Jakub Kicinski <kuba@kernel.org> + " David S. Miller <davem@davemloft.net>\0" "\00:1\0" "b\0" "On Thu, Sep 24, 2020 at 05:32:12PM +0200, Paul Menzel wrote:\n" @@ -16,7 +23,7 @@ "> Am 24.09.20 um 17:09 schrieb Kai-Heng Feng:\n" "> > We are seeing the following error after S3 resume:\n" "> \n" - "> I?d be great if you added the system and used hardware, you are seeing this\n" + "> I\342\200\231d be great if you added the system and used hardware, you are seeing this\n" "> with.\n" "> \n" "> > [ 704.746874] e1000e 0000:00:1f.6 eno1: Setting page 0x6020\n" @@ -24,10 +31,10 @@ "> \n" "> A follow-up patch, should extend the message to include the timeout value.\n" "> \n" - "> > MDI Write did not complete did not complete in ? seconds.\n" + "> > MDI Write did not complete did not complete in \342\200\246 seconds.\n" "> \n" - "> According to the Linux timestamps it?s 98 ms, which makes sense, as (640 * 3\n" - "> * 50 ?s = 96 ms).\n" + "> According to the Linux timestamps it\342\200\231s 98 ms, which makes sense, as (640 * 3\n" + "> * 50 \316\274s = 96 ms).\n" "> \n" "> What crappy hardware is this, that it takes longer than 100 ms?\n" "\n" @@ -43,4 +50,4 @@ "\n" Andrew -f70f05d18db829feb3cda725f41bd88af1abefce6f883c4a8b2af32ab4353689 +0e3656577b8c3aa16f377c5a619a08f838900c04742e95bc7cffbae4f4cc3c41
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.