From: "Linux kernel regression tracking (#update)" <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [Regression] Bug 216884 - NETDEV WATCHDOG: enp6s0 (r8169): transmit queue 0 timed out
Date: Sun, 15 Jan 2023 16:19:41 +0100 [thread overview]
Message-ID: <2a9140bb-8c4f-dda8-cf43-92db792a29db@leemhuis.info> (raw)
In-Reply-To: <f5b100c0-cdeb-59d1-5c82-e1df59ee3773@leemhuis.info>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 05.01.23 11:21, Linux kernel regression tracking (#adding) wrote:
> [TLDR: Just adding a regression reported to bko to the tracking]
>
> I noticed a regression reported in bugzilla.kernel.org that seems to be
> handled there already, nevertheless I'd like to add to the tracking to
> ensure it's doesn't fall through the cracks in the end:
>
> #regzbot introduced: v6.1..v6.2-rc2
> https://bugzilla.kernel.org/show_bug.cgi?id=216884
> #regzbot title: net: r8169: NETDEV WATCHDOG: enp6s0 (r8169): transmit
> queue 0 timed out
> #regzbot ignore-activity
#regzbot monitor:
https://lore.kernel.org/all/20230106095143.3158998-1-chenhuacai@loongson.cn/
#regzbot fix: PCI: loongson: Improve the MRRS quirk for LS7A
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2023-01-15 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 10:21 [Regression] Bug 216884 - NETDEV WATCHDOG: enp6s0 (r8169): transmit queue 0 timed out Linux kernel regression tracking (#adding)
2023-01-15 15:19 ` Linux kernel regression tracking (#update) [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=2a9140bb-8c4f-dda8-cf43-92db792a29db@leemhuis.info \
--to=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 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 NNTP newsgroup(s).