archive mirror
 help / color / mirror / Atom feed
From: "Linux regression tracking #update (Thorsten Leemhuis)" <>
To: Bagas Sanjaya <>,
	Linux Kernel Mailing List <>,
	Linux Regressions <>,
	Linux Kernel Network Developers <>,
	Linux BPF <>,
	Linux on Hyper-V <>
Cc: Michael Kelley <>,
	Haiyang Zhang <>,
	Paolo Abeni <>,
	"David S. Miller" <>,
	Jakub Kicinski <>
Subject: Re: Fwd: nvsp_rndis_pkt_complete error status and net_ratelimit: callbacks suppressed messages on 6.4.0rc4
Date: Mon, 19 Jun 2023 19:19:51 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]

On 30.05.23 14:25, Bagas Sanjaya wrote:
> I notice a regression report on Bugzilla [1]. Quoting from it:
> [...]
> #regzbot introduced: dca5161f9bd052
> #regzbot title: net_ratelimit and nvsp_rndis_pkt_complete error due to SEND_RNDIS_PKT status check
> Thanks.
> [1]:

#regzbot resolve: turned out it's not a regression, see
#regzbot ignore-activity

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
Everything you wanna know about Linux kernel regression tracking:
That page also explains what to do if mails like this annoy you.

#regzbot ignore-activity

      parent reply	other threads:[~2023-06-19 17:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 12:25 Fwd: nvsp_rndis_pkt_complete error status and net_ratelimit: callbacks suppressed messages on 6.4.0rc4 Bagas Sanjaya
2023-06-05 10:28 ` Linux regression tracking (Thorsten Leemhuis)
     [not found]   ` <>
2023-06-05 14:00     ` Bagas Sanjaya
2023-06-05 14:08   ` Michael Kelley (LINUX)
2023-06-19 17:19 ` Linux regression tracking #update (Thorsten Leemhuis) [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).