From: Mike Lothian <mike@fireburn.co.uk>
To: nbd@nbd.name
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org, lorenzo@kernel.org,
mikhail <mikhail.v.gavrilov@gmail.com>,
sujuan.chen@mediatek.com
Subject: Re: [6.2][regression] after commit cd372b8c99c5a5cf6a464acebb7e4a79af7ec8ae stopping working wifi mt7921e
Date: Tue, 17 Jan 2023 00:33:45 +0000 [thread overview]
Message-ID: <CAHbf0-EHP0cRDhOD_3Mf4aRzndoVYGbd3j3vxwUOh9_cHp+h1Q@mail.gmail.com> (raw)
Hi
I'm struggling to find these patches on Patchwork, or apply the saved
raw patches to rc4
If I'm missing them, would you mind posting the link
Cheers
Mike
next reply other threads:[~2023-01-17 0:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 0:33 Mike Lothian [this message]
2023-01-17 5:42 ` [6.2][regression] after commit cd372b8c99c5a5cf6a464acebb7e4a79af7ec8ae stopping working wifi mt7921e Mikhail Gavrilov
2023-01-17 6:42 ` Kalle Valo
2023-01-17 13:06 ` Mike Lothian
2023-01-17 13:13 ` Mikhail Gavrilov
-- strict thread matches above, loose matches on Subject: below --
2022-12-21 1:10 Mikhail Gavrilov
2022-12-21 10:45 ` Felix Fietkau
2022-12-21 11:26 ` Lorenzo Bianconi
2022-12-21 13:10 ` Mikhail Gavrilov
2022-12-21 14:12 ` Felix Fietkau
2022-12-21 16:07 ` Lorenzo Bianconi
2022-12-21 16:46 ` Mikhail Gavrilov
2022-12-21 17:17 ` Felix Fietkau
2022-12-22 6:47 ` Mikhail Gavrilov
2022-12-24 7:55 ` Thorsten Leemhuis
2022-12-26 10:59 ` Thorsten Leemhuis
2023-01-04 14:20 ` Thorsten Leemhuis
2023-01-09 7:32 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-10 7:16 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-10 8:00 ` Felix Fietkau
2023-01-10 8:41 ` Linux kernel regression tracking (Thorsten Leemhuis)
2023-01-13 14:11 ` Kalle Valo
2023-01-10 21:52 ` Mikhail Gavrilov
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=CAHbf0-EHP0cRDhOD_3Mf4aRzndoVYGbd3j3vxwUOh9_cHp+h1Q@mail.gmail.com \
--to=mike@fireburn.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=mikhail.v.gavrilov@gmail.com \
--cc=nbd@nbd.name \
--cc=sujuan.chen@mediatek.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).