From: z <zhaojunkui2008@126.com>
To: "Kalle Valo" <kvalo@kernel.org>
Cc: "Jakub Kicinski" <kubakici@wp.pl>,
"David S. Miller" <davem@davemloft.net>,
"Paolo Abeni" <pabeni@redhat.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
bernard@vivo.com
Subject: Re:Re: [PATCH] net/wireless: add debugfs exit function
Date: Fri, 22 Apr 2022 14:37:55 +0800 (CST) [thread overview]
Message-ID: <3c0443f.3b82.1804ffdcdeb.Coremail.zhaojunkui2008@126.com> (raw)
In-Reply-To: <877d7hoe2i.fsf@kernel.org>
Hi Kalle Valo:
>-----邮件原件-----
>发件人: Kalle Valo <kvalo@kernel.org>
>发送时间: 2022年4月22日 13:57
>收件人: Bernard Zhao <zhaojunkui2008@126.com>
>抄送: Jakub Kicinski <kubakici@wp.pl>; David S. Miller <davem@davemloft.net>; Paolo Abeni <pabeni@redhat.com>; Matthias Brugger <matthias.bgg@gmail.com>; linux-wireless@vger.kernel.org; netdev@vger.kernel.org; >linux-arm-kernel@lists.infradead.org; linux-mediatek@lists.infradead.org; linux-kernel@vger.kernel.org; 赵军奎 <bernard@vivo.com>
>主题: Re: [PATCH] net/wireless: add debugfs exit function
>Bernard Zhao <zhaojunkui2008@126.com> writes:
>> This patch add exit debugfs function to mt7601u.
>> Debugfs need to be cleanup when module is unloaded or load fail.
>"load fail"? Please be more specific, are you saying that the second module load fails or what?
For this part, there are two cases:
First when mt7601u is loaded, in function mt7601u_probe, if function mt7601u_probe run into error lable err_hw, mt7601u_cleanup didn`t cleanup the debugfs node.
Second when the module disconnect, in function mt7601u_disconnect, mt7601u_cleanup didn`t cleanup the debugfs node.
I think these are the mt7601u unloaded or load fail cases, but both with no debugfs cleanup work.
>> drivers/net/wireless/mediatek/mt7601u/debugfs.c | 9 +++++++--
>> drivers/net/wireless/mediatek/mt7601u/init.c | 1 +
>> drivers/net/wireless/mediatek/mt7601u/mt7601u.h | 1 +
>The title should be:
>mt7601u: add debugfs exit function
Got it, thanks!
>> --- a/drivers/net/wireless/mediatek/mt7601u/debugfs.c
>> +++ b/drivers/net/wireless/mediatek/mt7601u/debugfs.c
>> @@ -9,6 +9,8 @@
>> #include "mt7601u.h"
>> #include "eeprom.h"
>>
>> +static struct dentry *dir;
>How will this work when there are multiple mt7601u devices? Because of that, avoid using non-const static variables.
Sorry for missing this part, I understand that the better way is to manage it in the struct of the matched device, I would fix this in the next patch.
Thank you very much!
BR//Bernard
>--
>https://patchwork.kernel.org/project/linux-wireless/list/
>https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2022-04-22 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 1:28 [PATCH] net/wireless: add debugfs exit function Bernard Zhao
2022-04-22 5:57 ` Kalle Valo
2022-04-22 6:37 ` z [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=3c0443f.3b82.1804ffdcdeb.Coremail.zhaojunkui2008@126.com \
--to=zhaojunkui2008@126.com \
--cc=bernard@vivo.com \
--cc=davem@davemloft.net \
--cc=kubakici@wp.pl \
--cc=kvalo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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