From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: 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 15:48:00 -0400 [thread overview]
Message-ID: <20070314194800.GF3372@tuxdriver.com> (raw)
In-Reply-To: <20070314171742.GA20779-BwHGZ1snBHw4TRp0TYZeXw@public.gmane.org>
On Wed, Mar 14, 2007 at 05:17:42PM +0000, Jouni Malinen wrote:
> On Wed, Mar 14, 2007 at 12:03:56PM -0400, Kyle McMartin wrote:
> > Build-time debugging isn't overly useful for distro kernel folks, nor is
> > enabling huge amounts of debug spew by default. Provide the option of
> > enabling debugging with module parameters.
>
> While I understand that it would be difficult to change the debug level
> options with binary distributions, I'm not sure whether I would like to
> see these changes going in. PRISM2_NO_DEBUG was added to make it
> possible to reduce the driver size considerably. In addition, the change
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?
John
--
John W. Linville
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org
next prev parent reply other threads:[~2007-03-14 19:48 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 ` John W. Linville [this message]
[not found] ` <20070314194800.GF3372-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2007-03-14 22:05 ` [HOSTAP] " Jouni Malinen
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=20070314194800.GF3372@tuxdriver.com \
--to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
--cc=hostap-I1pBevtZXGcAvxtiuMwx3w@public.gmane.org \
--cc=j@w1.fi \
--cc=kyle-Z7WLFzj8eWMS+FvcfC7Uqw@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@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).