From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
netdev <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [regression] Bug 216397 - Kernel 5.19 with NetworkManager and iwd: Wifi reconnect on resume is broken #forregzbot
Date: Mon, 26 Sep 2022 15:40:53 +0200 [thread overview]
Message-ID: <d1ba88bf-ae0e-72e2-d5c8-133cd4323e9f@leemhuis.info> (raw)
In-Reply-To: <31cceaa5-2684-1aa8-61c6-c1be2d563bb0@leemhuis.info>
TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.
On 26.08.22 13:14, Thorsten Leemhuis wrote:
>
> To quote from https://bugzilla.kernel.org/show_bug.cgi?id=216397 :
>
>> Vorpal 2022-08-22 16:35:21 UTC
>>
>> Created attachment 301630 [details]
>> Relevant journalctl.txt
>>
>> After upgrading to kernel 5.19 (Arch Linux kernel, which is minimally modified, but I tested a few alternative kernels too, such as zen), wifi reconnect on resume is broken when using NetworkManager + iwd.
#regzbot fixed-by: 8997f5c8a62
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
prev parent reply other threads:[~2022-09-26 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 11:14 [regression] Bug 216397 - Kernel 5.19 with NetworkManager and iwd: Wifi reconnect on resume is broken Thorsten Leemhuis
2022-09-26 13:40 ` 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=d1ba88bf-ae0e-72e2-d5c8-133cd4323e9f@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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).