From: Joe Perches <joe@perches.com>
To: "Markus Böhme" <markus.boehme@mailbox.org>,
"Kalle Valo" <kvalo@codeaurora.org>,
"Dan Carpenter" <dan.carpenter@oracle.com>
Cc: devel@driverdev.osuosl.org, Ping-Ke Shih <pkshih@realtek.com>,
linux-wireless@vger.kernel.org,
Larry Finger <Larry.Finger@lwfinger.net>
Subject: Re: [PATCH 10/14] rtlwifi: Add BTC_TRACE_STRING to new btcoex
Date: Fri, 09 Dec 2016 22:39:34 -0800 [thread overview]
Message-ID: <1481351974.5946.49.camel@perches.com> (raw)
In-Reply-To: <77555ffb-de05-2837-2e13-aaf4ec710fc3@mailbox.org>
On Sat, 2016-12-10 at 00:56 +0100, Markus Böhme wrote:
> On 12/09/2016 09:50 AM, Kalle Valo wrote:
> > Dan Carpenter <dan.carpenter@oracle.com> writes:
> >
> > > On Thu, Dec 08, 2016 at 02:50:49PM +0300, Dan Carpenter wrote:
> > > > On Thu, Dec 08, 2016 at 01:43:42PM +0200, Kalle Valo wrote:
> > > > > But it would make me very happy if someone would add a similar grouping
> > > > > functionality to dyndbg to make it easy to enable a set of debug
> > > > > messages in a driver.
> > > >
> > > > Thats seems like a reasonable thing as well.
> > >
> > > I actually like the ath code... We could easily change it to be more
> > > generic and make it a top level function for everyone to use.
> >
> > That would be great. And maybe add a sysfs file with a description
> > different levels, like module parameters have. Too bad that I can't work
> > on that, too much stuff on my plate right now.
> >
>
> In this case I would like to step in and try to implement grouping of
> messages in the dynamic debug code. This seems to be an interesting
> learning opportunity.
Use bitmaps and levels.
next prev parent reply other threads:[~2016-12-10 6:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 1:48 [PATCH 00/14] rtlwifi: Various updates Larry Finger
2016-12-02 1:48 ` [PATCH 01/14] rtlwifi: Correct power save capability while init mac80211 Larry Finger
2016-12-30 13:10 ` [01/14] " Kalle Valo
2016-12-02 1:48 ` [PATCH 02/14] rtlwifi: Fix programing CAM content sequence Larry Finger
2016-12-05 20:49 ` Dan Carpenter
2016-12-02 1:48 ` [PATCH 03/14] rtlwifi: Set retry limit depends on vif type Larry Finger
2016-12-02 1:48 ` [PATCH 03/14] rtlwifi: extend debug_comp to u64 Larry Finger
2016-12-02 1:48 ` [PATCH 05/14] rtlwifi: Add TX report and disable key will wait until report acked Larry Finger
2016-12-05 21:10 ` Dan Carpenter
2016-12-02 1:48 ` [PATCH 06/14] rtlwifi: rtl8723be: btcoexist: Add single_ant_path Larry Finger
2016-12-02 1:48 ` [PATCH 07/14] rtlwifi: move btcoex's ant_num declaration Larry Finger
2016-12-02 1:48 ` [PATCH 08/14] rtlwifi: rtl8723be: btcoex: add package_type function to btcoex Larry Finger
2016-12-02 1:48 ` [PATCH 09/14] rtlwifi: ibtcoex: move bt_type declaration Larry Finger
2016-12-02 1:48 ` [PATCH 10/14] rtlwifi: Add BTC_TRACE_STRING to new btcoex Larry Finger
2016-12-05 21:34 ` Dan Carpenter
2016-12-05 22:34 ` Larry Finger
2016-12-06 7:13 ` Greg KH
2016-12-07 12:16 ` Kalle Valo
2016-12-07 13:32 ` Dan Carpenter
2016-12-07 16:41 ` Larry Finger
2016-12-08 11:43 ` Kalle Valo
2016-12-08 11:50 ` Dan Carpenter
2016-12-08 11:54 ` Dan Carpenter
2016-12-09 8:50 ` Kalle Valo
2016-12-09 23:56 ` Markus Böhme
2016-12-10 6:39 ` Joe Perches [this message]
2016-12-09 8:48 ` Kalle Valo
2016-12-06 19:37 ` Dan Carpenter
2016-12-02 1:48 ` [PATCH 11/14] rtlwifi: Add a new enumeration value to btc_set_type Larry Finger
2016-12-02 1:48 ` [PATCH 12/14] rtlwifi: btcoexist: Add vendor definition for new btcoexist Larry Finger
2016-12-02 1:48 ` [PATCH 13/14] rtlwifi: rtl8723be: fix ant_sel code Larry Finger
2016-12-02 1:48 ` [PATCH 14/14] rtlwifi: Add work queue for c2h cmd 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=1481351974.5946.49.camel@perches.com \
--to=joe@perches.com \
--cc=Larry.Finger@lwfinger.net \
--cc=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=markus.boehme@mailbox.org \
--cc=pkshih@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.