From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: "Jakub Kicinski" <kuba@kernel.org>,
"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: Thu, 11 May 2023 12:06:14 -0400 [thread overview]
Message-ID: <20230511-tart-asthma-girth-11164c@meerkat> (raw)
In-Reply-To: <71f119ab-24e2-6a35-2b7d-43ea2a9578b8@leemhuis.info>
On Thu, May 11, 2023 at 03:25:47PM +0200, Thorsten Leemhuis wrote:
> > 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?
>
> You missed that Konstantin (now CCed) is just a bit careful for the
> bugbot bring up and therefore for now only allows bugbot to be enabled
> for BZ entries that are filed against the product/component combination
> Linux/Kernel. I could reassigning bugs there, but that would break the
> workflow for maintainers like Kalle, which look at all bugs assigned to
> their product/component combo (Drivers/network-wireless in Kalle's case).
I hope to start opening this up to other products within the next few weeks,
as things are looking fairly stable for our initial tests.
-K
prev parent reply other threads:[~2023-05-11 16:06 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
2023-05-11 13:25 ` Thorsten Leemhuis
2023-05-11 16:06 ` Konstantin Ryabitsev [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=20230511-tart-asthma-girth-11164c@meerkat \
--to=konstantin@linuxfoundation.org \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hayeswang@realtek.com \
--cc=kuba@kernel.org \
--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