From: "Michael Kelley (LINUX)" <mikelley@microsoft.com>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Haiyang Zhang <haiyangz@microsoft.com>,
Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux BPF <bpf@vger.kernel.org>,
Linux on Hyper-V <linux-hyperv@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: RE: Fwd: nvsp_rndis_pkt_complete error status and net_ratelimit: callbacks suppressed messages on 6.4.0rc4
Date: Mon, 5 Jun 2023 14:08:06 +0000 [thread overview]
Message-ID: <BYAPR21MB16887C59D2B2C3ADDB61874BD74DA@BYAPR21MB1688.namprd21.prod.outlook.com> (raw)
In-Reply-To: <ebdd877d-f143-487c-04cd-606996eb6176@leemhuis.info>
From: Linux regression tracking (Thorsten Leemhuis) <regressions@leemhuis.info> Sent: Monday, June 5, 2023 3:28 AM
>
> Hi, Thorsten here, the Linux kernel's regression tracker.
>
> On 30.05.23 14:25, Bagas Sanjaya wrote:
> >
> > I notice a regression report on Bugzilla [1]. Quoting from it:
>
> Hmmm, nobody replied to this yet (or am I missing something?). Doesn't
> seems like it's something urgent, but nevertheless:
>
> Michael, Bagas didn't make it obvious at all, hence please allow me to
> ask: did you notice that this is a regression that is apparently caused
> by a commit of yours?
>
Thanks for flagging this directly to me. I'll check on it.
Michael
next prev parent reply other threads:[~2023-06-05 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 12:25 Bagas Sanjaya
2023-06-05 10:28 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-05 14:08 ` Michael Kelley (LINUX) [this message]
2023-06-19 17:19 ` Linux regression tracking #update (Thorsten Leemhuis)
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=BYAPR21MB16887C59D2B2C3ADDB61874BD74DA@BYAPR21MB1688.namprd21.prod.outlook.com \
--to=mikelley@microsoft.com \
--cc=bagasdotme@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=davem@davemloft.net \
--cc=haiyangz@microsoft.com \
--cc=kuba@kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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
all inboxes | Powered by JetHome®