From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: "chris.bainbridge@gmail.com" <chris.bainbridge@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"Korenblit, Miriam Rachel" <miriam.rachel.korenblit@intel.com>,
"Berg, Johannes" <johannes.berg@intel.com>,
"benjamin@sipsolutions.net" <benjamin@sipsolutions.net>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [REGRESSION] iwlwifi resume error, bisected
Date: Sun, 1 Jun 2025 05:46:24 +0000 [thread overview]
Message-ID: <0bfeda4daa039465e128a2eb375f09b585f47182.camel@intel.com> (raw)
In-Reply-To: <CAP-bSRb_PeuFMqOjJu=akYsYANQ2ek8N1oR=8RiPXBeefM5_NA@mail.gmail.com>
On Sat, 2025-05-31 at 22:24 +0100, Chris Bainbridge wrote:
> On Fri, 28 Mar 2025 at 04:24, Grumbach, Emmanuel
> <emmanuel.grumbach@intel.com> wrote:
> >
> > In any case, the patch will be reviewed internally and follow its
> > way
> > upstream following the regular process.
>
> Hi, did this patch ever get merged? I was just testing another issue
> and
> noticed that iwlwifi still dumps this error on resume in the latest
> 6.15
> mainline git on this particular laptop.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=15220a257319ffe3bf95796326dfe0aacdbeb1c4
It is included in 6.15.
next prev parent reply other threads:[~2025-06-01 5:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 13:19 [REGRESSION] iwlwifi resume error, bisected Chris Bainbridge
2024-09-07 18:35 ` Grumbach, Emmanuel
2024-09-07 21:21 ` Chris Bainbridge
2024-09-08 8:53 ` Grumbach, Emmanuel
2024-09-08 10:54 ` Grumbach, Emmanuel
2024-09-08 20:55 ` Chris Bainbridge
2024-09-09 3:07 ` Grumbach, Emmanuel
2024-09-09 16:16 ` Chris Bainbridge
2024-09-09 19:39 ` Grumbach, Emmanuel
2024-09-09 21:03 ` Chris Bainbridge
2024-09-10 9:23 ` Chris Bainbridge
2024-09-10 10:26 ` Grumbach, Emmanuel
2025-03-26 14:54 ` Chris Bainbridge
2025-03-26 16:36 ` Grumbach, Emmanuel
2025-03-27 0:35 ` Chris Bainbridge
2025-03-27 0:58 ` Chris Bainbridge
2025-03-27 3:35 ` Grumbach, Emmanuel
2025-03-27 20:31 ` Grumbach, Emmanuel
2025-03-27 21:36 ` Chris Bainbridge
2025-03-28 4:24 ` Grumbach, Emmanuel
2025-05-31 21:24 ` Chris Bainbridge
2025-06-01 5:46 ` Grumbach, Emmanuel [this message]
2025-06-02 16:11 ` Chris Bainbridge
2025-06-03 9:19 ` Grumbach, Emmanuel
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=0bfeda4daa039465e128a2eb375f09b585f47182.camel@intel.com \
--to=emmanuel.grumbach@intel.com \
--cc=benjamin@sipsolutions.net \
--cc=chris.bainbridge@gmail.com \
--cc=johannes.berg@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--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