ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karthikeyan Kathirvel <kathirve@codeaurora.org>
To: ath11k@lists.infradead.org
Cc: linux-wireless@vger.kernel.org,
	Karthikeyan Kathirvel <kathirve@codeaurora.org>
Subject: [PATCH] ath11k: removing the ath11k debugfs dir properly
Date: Wed, 23 Sep 2020 23:55:19 +0530	[thread overview]
Message-ID: <1600885519-29535-1-git-send-email-kathirve@codeaurora.org> (raw)

ath11k_debug_pdev_destroy was not called for proper cleaning of debug
files when destroying the pdev, this results in not removing the ath11k
directory in debugfs folder even after rmmod of ath11k. So when next
time doing insmod of ath11k prevents creating another ath11k directory,
hence causing ipq8074_2 to get created in parent dir of debugfs.

Signed-off-by: Karthikeyan Kathirvel <kathirve@codeaurora.org>
---
 drivers/net/wireless/ath/ath11k/debug.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/net/wireless/ath/ath11k/debug.c b/drivers/net/wireless/ath/ath11k/debug.c
index 0ba234a..c4759bb 100644
--- a/drivers/net/wireless/ath/ath11k/debug.c
+++ b/drivers/net/wireless/ath/ath11k/debug.c
@@ -973,6 +973,7 @@ void ath11k_debug_soc_destroy(struct ath11k_base *ab)
 {
 	debugfs_remove_recursive(ab->debugfs_soc);
 	ab->debugfs_soc = NULL;
+	ath11k_debug_pdev_destroy(ab);
 }
 
 void ath11k_debug_fw_stats_init(struct ath11k *ar)
-- 
2.7.4


-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

             reply	other threads:[~2020-09-23 18:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-23 18:25 Karthikeyan Kathirvel [this message]
2020-09-24 16:16 ` [PATCH] ath11k: removing the ath11k debugfs dir properly Kalle Valo
     [not found] ` <20200924161623.ED696C433F1@smtp.codeaurora.org>
2020-09-29 19:21   ` kathirve

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=1600885519-29535-1-git-send-email-kathirve@codeaurora.org \
    --to=kathirve@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    /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