From: "Linux regression tracking #adding (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Vegard Nossum <vegard.nossum@oracle.com>,
Alexander Wetzel <alexander@wetzel-home.de>,
Thomas Mann <rauchwolke@gmx.net>,
linux-wireless@vger.kernel.org
Cc: Johannes Berg <johannes.berg@intel.com>, regressions@lists.linux.dev
Subject: Re: iwlwifi frequent drops between v6.2-rc3 and v6.3-rc1
Date: Wed, 22 Mar 2023 14:59:38 +0100 [thread overview]
Message-ID: <d1c9a828-bb20-bfa8-fb37-bbc3f57b4cfd@leemhuis.info> (raw)
In-Reply-To: <9d11ed29-1114-055d-5b26-0899a5fc0d7f@oracle.com>
[TLDR: I'm adding this report to the list of tracked Linux kernel
regressions; the text you find below is based on a few templates
paragraphs you might have encountered already in similar form.
See link in footer if these mails annoy you.]
On 17.03.23 09:53, Vegard Nossum wrote:
>
> Somewhere between e8f60cd7db24 (v6.2-rc3) and 2eb29d59ddf0 (v6.3-rc1) my
> wifi started dropping a lot. I'm using iwlwifi and I've checked the old
> logs that the firmware hasn't changed:
Thanks for the report. Due to Alexander's reply I hesitated first to add
this regression to the tracking, as I wondered that this might solve
itself quickly. But well, nothing happened since then, so I guess I
better add it to ensure the issue doesn't fall through the cracks:
#regzbot ^introduced e8f60cd7db24..2eb29d59ddf0
#regzbot title iwlwifi: frequent drops between v6.2-rc3 and v6.3-rc1
#regzbot ignore-activity
This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.
Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (the parent of this mail). See page linked in footer for
details.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2023-03-22 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-17 8:53 iwlwifi frequent drops between v6.2-rc3 and v6.3-rc1 Vegard Nossum
2023-03-17 15:29 ` Alexander Wetzel
2023-03-25 20:33 ` Alexander Wetzel
2023-04-12 11:38 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-16 12:40 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-03-22 13:59 ` Linux regression tracking #adding (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:
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=d1c9a828-bb20-bfa8-fb37-bbc3f57b4cfd@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=alexander@wetzel-home.de \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rauchwolke@gmx.net \
--cc=regressions@lists.linux.dev \
--cc=vegard.nossum@oracle.com \
/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).