From: Joe Perches <joe@perches.com>
To: Larry Finger <Larry.Finger@lwfinger.net>, kvalo@codeaurora.org
Cc: linux-wireless@vger.kernel.org, Ping-Ke Shih <pkshih@realtek.com>,
Yan-Hsuan Chuang <yhchuang@realtek.com>,
Birming Chiu <birming@realtek.com>, Shaofu <shaofu@realtek.com>,
Steven Ting <steventing@realtek.com>
Subject: Re: [PATCH v2 09/10] rtlwifi: use debugfs to debug.
Date: Mon, 14 Aug 2017 17:59:44 -0700 [thread overview]
Message-ID: <1502758784.8295.30.camel@perches.com> (raw)
In-Reply-To: <9007f821-764b-9bd5-da13-bcbd032e57e1@lwfinger.net>
On Mon, 2017-08-14 at 16:17 -0500, Larry Finger wrote:
> On 08/14/2017 01:56 PM, Joe Perches wrote:
> > On Sun, 2017-06-25 at 10:43 -0500, Larry Finger wrote:
> > > From: Ping-Ke Shih <pkshih@realtek.com>
> > >
> > > Use debugfs to dump register and btcoex status.
> >
> > []
> > > diff --git a/drivers/net/wireless/realtek/rtlwifi/debug.c b/drivers/net/wireless/realtek/rtlwifi/debug.c
> >
> > []
> > > +void rtl_debug_add_one(struct ieee80211_hw *hw)
> > > +{
> > > + struct rtl_priv *rtlpriv = rtl_priv(hw);
> > > + struct rtl_efuse *rtlefuse = rtl_efuse(rtl_priv(hw));
> > > + struct dentry *parent;
> > > +
> > > + snprintf(rtlpriv->dbg.debugfs_name, 18, "%02x-%02x-%02x-%02x-%02x-%02x",
> > > + rtlefuse->dev_addr[0], rtlefuse->dev_addr[1],
> > > + rtlefuse->dev_addr[2], rtlefuse->dev_addr[3],
> > > + rtlefuse->dev_addr[4], rtlefuse->dev_addr[5]);
> >
> > Why uses dashes and why not just use %pM
>
> This snprintf() supplies the MAC address in a file name of the type
> /sys/kernel/debug/rtlwifi/00-11-22-33-44-55-66/mac_0
> Using %pM would put colons there, and I have had trouble with colons in a file
> name. We could use %#pM and drop the separators.
%pm emits without colons
next prev parent reply other threads:[~2017-08-15 0:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-25 15:43 [PATCH v2 00/10] Set 3 of changes related to updates of btcoexist Larry Finger
2017-06-25 15:43 ` [PATCH v2 01/10] rtlwifi: Fill in_4way field by driver Larry Finger
2017-06-25 15:43 ` [PATCH v2 02/10] rtlwifi: Add BT_MP_INFO to c2h handler Larry Finger
2017-06-25 15:43 ` [PATCH v2 03/10] rtlwifi: Add board type for 8723be and 8192ee Larry Finger
2017-06-25 15:43 ` [PATCH v2 04/10] rtlwifi: add amplifier type for 8812ae Larry Finger
2017-06-25 15:43 ` [PATCH v2 05/10] rtlwifi: Update 8723be new phy parameters and its parser Larry Finger
2017-06-25 15:43 ` [PATCH v2 06/10] rtlwifi: Rename rtl_desc92_rate to rtl_desc_rate Larry Finger
2017-06-25 15:43 ` [PATCH v2 07/10] rtlwifi: Uses addr1 instead DA to determine broadcast and multicast addr Larry Finger
2017-06-25 15:43 ` [PATCH v2 08/10] rtlwifi: move IS_HARDWARE_TYPE_xxx checker to wifi.h Larry Finger
2017-06-25 15:43 ` [PATCH v2 09/10] rtlwifi: use debugfs to debug Larry Finger
2017-08-14 18:56 ` Joe Perches
2017-08-14 19:08 ` Arend van Spriel
2017-08-14 21:19 ` Larry Finger
2017-08-14 21:17 ` Larry Finger
2017-08-15 0:59 ` Joe Perches [this message]
2017-06-25 15:43 ` [PATCH v2 10/10] rtlwifi: btcoex: Use seq_file to dump btcoex status Larry Finger
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=1502758784.8295.30.camel@perches.com \
--to=joe@perches.com \
--cc=Larry.Finger@lwfinger.net \
--cc=birming@realtek.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
--cc=shaofu@realtek.com \
--cc=steventing@realtek.com \
--cc=yhchuang@realtek.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).