From: Kalle Valo <kvalo@kernel.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: enc0der <enc0der@gmail.com>,
"Linux Regressions" <regressions@lists.linux.dev>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Wireless" <linux-wireless@vger.kernel.org>,
"Linux Networking" <netdev@vger.kernel.org>,
"Linux USB" <linux-usb@vger.kernel.org>,
"Linux RCU" <rcu@vger.kernel.org>,
"Stanislaw Gruszka" <stf_xl@wp.pl>,
"Helmut Schaa" <helmut.schaa@googlemail.com>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Hayes Wang" <hayeswang@realtek.com>,
"Simon Horman" <horms@kernel.org>,
"Andre Przywara" <andre.przywara@arm.com>,
"Andrew Gaul" <gaul@gaul.org>, "Bjørn Mork" <bjorn@mork.no>,
"Paul E. McKenney" <paulmck@kernel.org>,
"Frederic Weisbecker" <frederic@kernel.org>,
"Neeraj Upadhyay" <quic_neeraju@quicinc.com>,
"Joel Fernandes" <joel@joelfernandes.org>,
"Josh Triplett" <josh@joshtriplett.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Mathieu Desnoyers" <mathieu.desnoyers@efficios.com>,
"Lai Jiangshan" <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang1211@gmail.com>
Subject: Re: rt8000usb driver issue (maybe interaction with other drivers)
Date: Tue, 03 Oct 2023 08:47:00 +0300 [thread overview]
Message-ID: <878r8ki7fv.fsf@kernel.org> (raw)
In-Reply-To: <3d246a72-2755-484f-8274-0c61fc185592@gmail.com> (Bagas Sanjaya's message of "Sun, 1 Oct 2023 12:53:22 +0700")
Bagas Sanjaya <bagasdotme@gmail.com> writes:
>> These are the drivers being loaded:
>>
>> rt2800usb 36864 0
>> rt2x00usb 24576 1 rt2800usb
>> rt2800lib 122880 1 rt2800usb
>> rt2x00lib 77824 3 rt2800usb,rt2x00usb,rt2800lib
>> mac80211 811008 3 rt2x00lib,rt2x00usb,rt2800lib
>> cfg80211 724992 2 rt2x00lib,mac80211
>>
>
> I don't see rt2800usb module in the mainline kernel. Is it out-of-tree?
> (no wonder why it taints your kernel)
I'm guessing it's this driver:
drivers/net/wireless/ralink/rt2x00/Makefile:obj-$(CONFIG_RT2800USB) += rt2800usb.o
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2023-10-03 5:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEXpi5Rd6Y4umKOWRsCjX0kit=W5ZrVhn=MuRkyvJPwmjjDVnA@mail.gmail.com>
2023-10-01 5:12 ` rt8000usb driver issue (maybe interaction with other drivers) Bagas Sanjaya
2023-10-01 5:33 ` enc0der
2023-10-01 5:53 ` Bagas Sanjaya
2023-10-03 5:47 ` Kalle Valo [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=878r8ki7fv.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=andre.przywara@arm.com \
--cc=bagasdotme@gmail.com \
--cc=bjorn@mork.no \
--cc=boqun.feng@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enc0der@gmail.com \
--cc=frederic@kernel.org \
--cc=gaul@gaul.org \
--cc=hayeswang@realtek.com \
--cc=helmut.schaa@googlemail.com \
--cc=horms@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=stf_xl@wp.pl \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).