From: Forty Five <mathewegeorge@gmail.com>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Bernie Huang <phhuang@realtek.com>,
"kvalo@kernel.org" <kvalo@kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: RE: [REGRESSION] Freeze on resume from S3 (bisected)
Date: Mon, 08 Jul 2024 22:00:29 +0530 [thread overview]
Message-ID: <87h6czdexm.fsf@gmail.com> (raw)
In-Reply-To: <draft-87msmrdgkb.fsf@gmail.com>
> I'll get to work on the bisection, and send the log here when it's
> done.
Just to confirm - I should apply [1], and no other patches, during the
bisection, right?
[1] https://lore.kernel.org/linux-wireless/20240517013350.11278-1-pkshih@realtek.com/
next parent reply other threads:[~2024-07-08 16:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <draft-87msmrdgkb.fsf@gmail.com>
2024-07-08 16:30 ` Forty Five [this message]
2024-07-09 1:26 ` [REGRESSION] Freeze on resume from S3 (bisected) Ping-Ke Shih
2024-07-09 4:10 ` Forty Five
2024-07-09 4:25 ` Ping-Ke Shih
2024-07-09 11:49 ` Forty Five
2024-07-11 7:54 ` Forty Five
2024-07-12 0:59 ` Ping-Ke Shih
2024-07-08 15:55 Forty Five
-- strict thread matches above, loose matches on Subject: below --
2024-07-01 6:15 Forty Five
[not found] <875xtqjli4.fsf@gmail.com>
2024-06-30 19:20 ` Forty Five
2024-07-01 2:46 ` Ping-Ke Shih
2024-07-01 5:36 ` Ping-Ke Shih
2024-06-30 19:11 Forty Five
2024-07-03 7:39 ` Ping-Ke Shih
2024-06-19 4:39 Forty Five
2024-06-19 6:07 ` Ping-Ke Shih
2024-06-19 14:46 ` Forty Five
2024-06-20 8:16 ` Ping-Ke Shih
2024-06-20 8:56 ` Kalle Valo
2024-06-20 9:06 ` Ping-Ke Shih
2024-06-20 9:18 ` Mathew George
2024-06-20 9:33 ` Ping-Ke Shih
2024-06-20 10:05 ` Mathew George
2024-06-20 11:41 ` Ping-Ke Shih
2024-06-20 11:58 ` Johannes Berg
2024-06-20 13:05 ` Forty Five
2024-06-20 13:41 ` Forty Five
2024-06-28 3:55 ` Ping-Ke Shih
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=87h6czdexm.fsf@gmail.com \
--to=mathewegeorge@gmail.com \
--cc=kvalo@kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=phhuang@realtek.com \
--cc=pkshih@realtek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.