From: Johannes Berg <johannes@sipsolutions.net>
To: Arend van Spriel <arend.vanspriel@broadcom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: debugfs entries in cfg80211
Date: Fri, 09 Mar 2018 10:59:15 +0200 [thread overview]
Message-ID: <bea697dacbe725c636c5dfdd12d7ab2b@sipsolutions.net> (raw)
In-Reply-To: <5A9D034D.9060203@broadcom.com> (sfid-20180305_094401_329661_B11F6C32)
Hi Arend,
Sorry for the late reply - just returning from Israel now (in fact I'm
on the plane, but it has wifi).
> While reworking brcmfmac I stumbled on debugfs code in cfg80211, which
> creates the debugfs dir for the wiphy instance. It also creates a
> couple of entries, ie. rts and fragmentation threshold and retry
> limits. How useful are these as I suspect it is pretty old cruft and
> iw can obtain the information as well. Can it be removed.
No objection from me to removing them!
johannes
prev parent reply other threads:[~2018-03-09 8:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 8:43 debugfs entries in cfg80211 Arend van Spriel
2018-03-09 8:59 ` Johannes Berg [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=bea697dacbe725c636c5dfdd12d7ab2b@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=arend.vanspriel@broadcom.com \
--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;
as well as URLs for NNTP newsgroup(s).