regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	Johannes Berg <johannes@sipsolutions.net>
Subject: Re: Bug 215523 - Firmware crash with 66.f1c864e0.0 (cc-a0-66.ucode) and 68.01d30b0c (cc-a0-68.ucode)
Date: Tue, 1 Mar 2022 09:07:23 -0800	[thread overview]
Message-ID: <20220301090723.762f607e@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net> (raw)
In-Reply-To: <adf5ac57-cd60-a004-a05d-6d7c3ad7efa7@leemhuis.info>

On Thu, 10 Feb 2022 10:56:13 +0100 Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker speaking.
> 
> There is a regression in bugzilla.kernel.org I'd like to add to the
> tracking:
> 
> #regzbot introduced: v5.16..v5.17-rc1
> #regzbot from: Udo Steinberg <udo@hypervisor.org>
> #regzbot title: iwlwifi: Firmware crash with 66.f1c864e0.0
> (cc-a0-66.ucode) and 68.01d30b0c (cc-a0-68.ucode)
> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215523

Hi Thorsten, does regzbot follow the additional links? Or do we always
need the fix to link to the original report? 
No preference - just clarifying.

#regzbot fixed-by: 1db5fcbba2631277b78

  parent reply	other threads:[~2022-03-01 17:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10  9:56 Bug 215523 - Firmware crash with 66.f1c864e0.0 (cc-a0-66.ucode) and 68.01d30b0c (cc-a0-68.ucode) Thorsten Leemhuis
2022-02-25 15:10 ` Thorsten Leemhuis
2022-03-01 17:07 ` Jakub Kicinski [this message]
2022-03-01 17:51   ` 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=20220301090723.762f607e@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net \
    --to=kuba@kernel.org \
    --cc=johannes@sipsolutions.net \
    --cc=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).