From: Jakub Kicinski <kuba@kernel.org>
To: "Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>
Cc: "Linux regressions mailing list" <regressions@lists.linux.dev>,
"Bjørn Mork" <bjorn@mork.no>,
"Hayes Wang" <hayeswang@realtek.com>,
netdev@vger.kernel.org, "Paolo Abeni" <pabeni@redhat.com>,
"Eric Dumazet" <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
"Stanislav Fomichev" <sdf@fomichev.me>,
workflows@vger.kernel.org
Subject: Re: [regression] Kernel OOPS on boot with Kernel 6.3(.1) and RTL8153 Gigabit Ethernet Adapter
Date: Mon, 8 May 2023 13:09:44 -0700 [thread overview]
Message-ID: <20230508130944.30699c33@kernel.org> (raw)
In-Reply-To: <9284a9ec-d7c9-68e8-7384-07291894937b@leemhuis.info>
On Sat, 6 May 2023 08:20:23 +0200 Linux regression tracking (Thorsten
Leemhuis) wrote:
> > I don't seem to have the permissions on BZ, but I'm guessing we could
> > do the opposite - you could flip bugbot on first to have it flush the BZ
> > report to the list, and then reply on the list with regzbot tracking?
>
> That's the plan for the future, but for now I don't want to do that, as
> it might mess up other peoples workflows, as hinted above already and
> discussed here:
>
> https://lore.kernel.org/all/1f0ebf13-ab0f-d512-6106-3ebf7cb372f1@leemhuis.info/
>
> That was only recently, but if you jump in there as well it might
> persuade Konstantin to enable bugbot for other products/components. Then
> I could and would do what you suggested.
CC: workflows
I'm a bit confused. I understand that we don't want to automatically
send all bugzilla reports to the ML. But AFAIU this is to avoid spamming
the list / messing with people's existing BZ workflow.
If you pre-triage the problem and decide to forward it to the list -
whether you do it with buzbot + regzbot or manual + regzbot is moot.
The bugbot can be enabled per BZ entry (AFAIU), so you can flip it
individually for the thread you want to report. It should flush that
BZ to the list. At which point you can follow your normal ML regression
process.
Where did I go off the rails?
next parent reply other threads:[~2023-05-08 20:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ec4be122-e213-ca5b-f5d6-e8f9c3fd3bee@leemhuis.info>
[not found] ` <87lei36q27.fsf@miraculix.mork.no>
[not found] ` <20230505120436.6ff8cfca@kernel.org>
[not found] ` <57dbce31-daa9-9674-513e-f123b94950da@leemhuis.info>
[not found] ` <20230505123744.16666106@kernel.org>
[not found] ` <9284a9ec-d7c9-68e8-7384-07291894937b@leemhuis.info>
2023-05-08 20:09 ` Jakub Kicinski [this message]
2023-05-11 13:25 ` [regression] Kernel OOPS on boot with Kernel 6.3(.1) and RTL8153 Gigabit Ethernet Adapter Thorsten Leemhuis
2023-05-11 16:06 ` Konstantin Ryabitsev
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=20230508130944.30699c33@kernel.org \
--to=kuba@kernel.org \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hayeswang@realtek.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sdf@fomichev.me \
--cc=workflows@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).