netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jouni Malinen <j@w1.fi>
To: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
Cc: Kyle McMartin <kyle-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org>,
	linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	hostap-I1pBevtZXGcAvxtiuMwx3w@public.gmane.org, j@w1.fi
Subject: Re: [HOSTAP] Make debug a run-time option
Date: Wed, 14 Mar 2007 22:05:38 +0000	[thread overview]
Message-ID: <20070314220538.GA23642@hostap.isc.org> (raw)
In-Reply-To: <20070314194800.GF3372-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>

On Wed, Mar 14, 2007 at 03:48:00PM -0400, John W. Linville wrote:

> What about a combined approach?  The existing compile-time option
> could remain while runtime restrictions could be added for when the
> debug stuff is compiled into the driver?

I would be perfectly fine with doing that assuming the default behavior
is not changed with this patch (i.e., debugging would be enabled by
default). I would consider changing the default setting a separate issue
and for that, it might be more worthwhile approach to identify the debug
messages that are undesired by default than to disable everything.

-- 
Jouni Malinen                                            PGP id EFC895FA

      parent reply	other threads:[~2007-03-14 22:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-14 16:03 [HOSTAP] Make debug a run-time option Kyle McMartin
2007-03-14 17:17 ` Jouni Malinen
     [not found]   ` <20070314171742.GA20779-BwHGZ1snBHw4TRp0TYZeXw@public.gmane.org>
2007-03-14 19:48     ` [HOSTAP] " John W. Linville
     [not found]       ` <20070314194800.GF3372-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-03-14 22:05         ` Jouni Malinen [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=20070314220538.GA23642@hostap.isc.org \
    --to=j@w1.fi \
    --cc=hostap-I1pBevtZXGcAvxtiuMwx3w@public.gmane.org \
    --cc=kyle-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
    --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org \
    --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).