All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Maxim Levitsky <mlevitsk@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, Hayes Wang <hayeswang@realtek.com>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: Commit 'r8152: fix a WOL issue' makes Ethernet port on Lenovo Thunderbolt 3 dock go crazy
Date: Thu, 25 Aug 2022 09:13:43 -0700	[thread overview]
Message-ID: <20220825091343.2e5f99dd@kernel.org> (raw)
In-Reply-To: <8c214c0b-4b8f-5e62-5aef-76668987e8fd@leemhuis.info>

On Thu, 25 Aug 2022 09:26:21 +0200 Thorsten Leemhuis wrote:
> On 24.08.22 13:16, Thorsten Leemhuis wrote:
> > Hi, this is your Linux kernel regression tracker.
> > 
> > Quick note before the boilerplate: there is another report about issues
> > caused by cdf0b86b250fd3 also involving a dock, but apparently it's
> > ignored so far:
> > https://bugzilla.kernel.org/show_bug.cgi?id=216333  
> 
> TWIMC, apparently it's the same problem.
> 
> Fun fact: Hayes discussed this in privately with the bug reporter
> according to this comment:
> https://bugzilla.kernel.org/show_bug.cgi?id=216333#c3
> 
> Well, that's not how things normally should be handled, but whatever, he
> in the end recently submitted a patch to fix it that is already merged
> to net.git:
> 
> https://lore.kernel.org/lkml/20220818080620.14538-394-nic_swsd@realtek.com/

Yup, it will be part of 6.0-rc3. 

Thanks!

  reply	other threads:[~2022-08-25 16:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23  9:20 Commit 'r8152: fix a WOL issue' makes Ethernet port on Lenovo Thunderbolt 3 dock go crazy Maxim Levitsky
2022-08-24 11:16 ` Thorsten Leemhuis
2022-08-25  7:26   ` Thorsten Leemhuis
2022-08-25 16:13     ` Jakub Kicinski [this message]
2022-08-26  7:49       ` Thorsten Leemhuis
2022-08-30  9:28         ` Maxim Levitsky

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=20220825091343.2e5f99dd@kernel.org \
    --to=kuba@kernel.org \
    --cc=hayeswang@realtek.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mlevitsk@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    /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.