linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Arend van Spriel" <arend@broadcom.com>
To: "Seth Forshee" <seth.forshee@canonical.com>
Cc: linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
	"Brett Rudley" <brudley@broadcom.com>,
	"Roland Vossen" <rvossen@broadcom.com>,
	"Kan Yan" <kanyan@broadcom.com>,
	brcm80211-dev-list@broadcom.com
Subject: Re: [PATCH 00/18] brcmsmac: Tx rework and expanded debug/trace support
Date: Wed, 14 Nov 2012 20:40:59 +0100	[thread overview]
Message-ID: <50A3F3CB.4040402@broadcom.com> (raw)
In-Reply-To: <20121114160559.GA18738@thinkpad-t410>

On 11/14/2012 05:05 PM, Seth Forshee wrote:
> Hi Arend,
>
> I've got v2 patches prepped with your request changes, which I'll send
> as soon as I'm finished testing. I did have a question about one of your
> requests though.
>
> On Sun, Nov 04, 2012 at 09:25:49PM +0100, Seth Forshee wrote:
>> On Sat, Nov 03, 2012 at 06:56:43PM +0100, Arend van Spriel wrote:
>>>>    brcmsmac: Add module parameter for setting the debug level
>>>
>>> I would prefer doing this through debugfs.
>
> I mentioned this to you at the wireless summit. If this is moved to
> debugfs it will not allow for setting the debug level at module load
> time. If we leave it a module parameter it can still be set at runtime
> via /sys/module/parameters/brcmsmac/debug, assuming BRCMDBG is enabled.
> I currently don't have this change in my v2 patches, but if you still
> want it changed to debugfs let me know and I'll take care of it.
>
> Thanks,
> Seth

Indeed we discussed it. I do not have a strong preference and having it 
set during module init has its perks. So you can leave it as it is. I am 
looking forward to your v2 patches ;-)

Gr. AvS



  reply	other threads:[~2012-11-14 19:41 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-26 14:23 [PATCH 00/18] brcmsmac: Tx rework and expanded debug/trace support Seth Forshee
2012-10-26 14:23 ` [PATCH 01/18] brcmsmac: Rework tx code to avoid internal buffering of packets Seth Forshee
2012-11-01 17:43   ` Arend van Spriel
2012-11-02  7:28     ` Seth Forshee
2012-10-26 14:23 ` [PATCH 02/18] brcmsmac: Use correct descriptor count when calculating next rx descriptor Seth Forshee
2012-10-26 14:23 ` [PATCH 03/18] brcmsmac: Reduce number of entries in tx DMA rings Seth Forshee
2012-10-26 14:23 ` [PATCH 04/18] brcm80211: Allow trace support to be enabled separately from debug Seth Forshee
2012-10-26 14:23 ` [PATCH 05/18] brcm80211: Add macro for checking if debug log levels are enabled Seth Forshee
2012-10-26 14:23 ` [PATCH 06/18] brcm80211: Convert log message levels to debug levels Seth Forshee
2012-10-26 14:23 ` [PATCH 07/18] brcmsmac: Add module parameter for setting the debug level Seth Forshee
2012-10-26 14:23 ` [PATCH 08/18] brcmsmac: Add support for writing debug messages to the trace buffer Seth Forshee
2012-10-26 14:23 ` [PATCH 09/18] brcmsmac: Use debug macros for general error and debug statements Seth Forshee
2012-10-26 14:23 ` [PATCH 10/18] brcmsmac: Add BRCMS_DBG_MAC80211 debug macro Seth Forshee
2012-10-26 14:23 ` [PATCH 11/18] brcmsmac: Add RX and TX debug macros Seth Forshee
2012-10-26 14:23 ` [PATCH 12/18] brcmsmac: Add INT debug macro Seth Forshee
2012-10-26 14:23 ` [PATCH 13/18] brcmsmac: Add DMA " Seth Forshee
2012-10-26 14:23 ` [PATCH 14/18] brcmsmac: Add HT " Seth Forshee
2012-10-26 14:23 ` [PATCH 15/18] brcmsmac: Improve tx trace and debug support Seth Forshee
2012-10-26 14:23 ` [PATCH 16/18] brcmsmac: Add tracepoint for macintstatus Seth Forshee
2012-10-26 14:23 ` [PATCH 17/18] brcmsmac: Add tracepoint for AMPDU session information Seth Forshee
2012-10-26 14:23 ` [PATCH 18/18] brcmsmac: Remove some noisy but uninformative debug messages Seth Forshee
2012-10-26 15:37 ` [PATCH 00/18] brcmsmac: Tx rework and expanded debug/trace support Arend van Spriel
2012-10-26 16:04   ` Seth Forshee
2012-11-02 10:49 ` Karl Beldan
2012-11-03 11:15   ` Johannes Berg
2012-11-03 13:50     ` Karl Beldan
2012-11-04 20:11       ` Seth Forshee
2012-11-03 17:56 ` Arend van Spriel
2012-11-04 20:25   ` Seth Forshee
2012-11-14 16:05     ` Seth Forshee
2012-11-14 19:40       ` Arend van Spriel [this message]
2012-11-06  7:12 ` Daniel Wagner
2012-11-06  8:19   ` Daniel Wagner
2012-11-06 10:02     ` Seth Forshee
2012-11-06 12:16       ` Daniel Wagner
2012-11-06 12:47         ` Seth Forshee
2012-11-06 12:49           ` Arend van Spriel
2012-11-06 10:20     ` Arend van Spriel
2012-11-06 10:44       ` Piotr Haber
2012-11-06 12:27         ` Daniel Wagner
2012-11-06 12:54           ` Seth Forshee

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=50A3F3CB.4040402@broadcom.com \
    --to=arend@broadcom.com \
    --cc=brcm80211-dev-list@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=frankyl@broadcom.com \
    --cc=kanyan@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=rvossen@broadcom.com \
    --cc=seth.forshee@canonical.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).