From: Mike Lothian <mike@fireburn.co.uk>
To: khalid@gonehiking.org
Cc: Deren.Wu@mediatek.com, Eddie.Chen@mediatek.com,
Eric-SY.Chang@mediatek.com, Eric.Liang@mediatek.com,
Leon.Yen@mediatek.com, Mark-YW.Chen@mediatek.com,
Soul.Huang@mediatek.com, Stella.Chang@mediatek.com,
Tom.Chou@mediatek.com, YN.Chen@mediatek.com,
abhishekpandit@google.com, ch.yeh@mediatek.com,
frankgor@google.com, jemele@google.com, jenhao.yang@mediatek.com,
jsiuda@google.com, km.lin@mediatek.com,
linux-mediatek@lists.infradead.org,
linux-wireless@vger.kernel.org, lorenzo.bianconi@redhat.com,
nbd@nbd.name, posh.sun@mediatek.com, robin.chiu@mediatek.com,
sean.wang@mediatek.com, shawnku@google.com,
steve.lee@mediatek.com, ted.huang@mediatek.com
Subject: Re: [PATCH] mt76: mt7921e: fix possible probe failure after reboot
Date: Thu, 20 Jan 2022 09:56:22 +0000 [thread overview]
Message-ID: <20220120095622.1938-1-mike@fireburn.co.uk> (raw)
In-Reply-To: <d291f592-d84a-2ffe-7f75-df77890efce8@gonehiking.org>
Hi
I get a BUG and the kernel resuses to boot with this patch when mt76 is compiled into the kernel
https://bugzilla.kernel.org/show_bug.cgi?id=214557
I don't see this issue when mt76 is compiled as a module
My .config is at https://github.com/FireBurn/KernelStuff/blob/master/dot_config_tip
Let me know if you'd like any more info
Cheers
Mike
next prev parent reply other threads:[~2022-01-20 9:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-07 7:30 [PATCH] mt76: mt7921e: fix possible probe failure after reboot sean.wang
2022-01-18 18:16 ` Khalid Aziz
2022-01-20 9:56 ` Mike Lothian [this message]
2022-01-25 14:16 ` Mike Lothian
2022-01-25 18:09 ` Ben Greear
2022-01-25 22:56 ` Mike Lothian
2022-02-24 16:54 ` Mike Lothian
2022-01-21 6:33 ` Janusz Dziedzic
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=20220120095622.1938-1-mike@fireburn.co.uk \
--to=mike@fireburn.co.uk \
--cc=Deren.Wu@mediatek.com \
--cc=Eddie.Chen@mediatek.com \
--cc=Eric-SY.Chang@mediatek.com \
--cc=Eric.Liang@mediatek.com \
--cc=Leon.Yen@mediatek.com \
--cc=Mark-YW.Chen@mediatek.com \
--cc=Soul.Huang@mediatek.com \
--cc=Stella.Chang@mediatek.com \
--cc=Tom.Chou@mediatek.com \
--cc=YN.Chen@mediatek.com \
--cc=abhishekpandit@google.com \
--cc=ch.yeh@mediatek.com \
--cc=frankgor@google.com \
--cc=jemele@google.com \
--cc=jenhao.yang@mediatek.com \
--cc=jsiuda@google.com \
--cc=khalid@gonehiking.org \
--cc=km.lin@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
--cc=posh.sun@mediatek.com \
--cc=robin.chiu@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shawnku@google.com \
--cc=steve.lee@mediatek.com \
--cc=ted.huang@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).