From: Kalle Valo <kvalo@codeaurora.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org,
Yan-Hsuan Chuang <yhchuang@realtek.com>,
Pkshih <pkshih@realtek.com>, Birming Chiu <birming@realtek.com>,
Shaofu <shaofu@realtek.com>, Steven Ting <steventing@realtek.com>
Subject: Re: [PATCH v2 0/4] rtlwifi: btcoex: Remove all references to BT_AUTO_REPORT_ONLY* parameters
Date: Thu, 11 May 2017 14:46:50 +0300 [thread overview]
Message-ID: <87a86jvcnp.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20170504184701.16560-1-Larry.Finger@lwfinger.net> (Larry Finger's message of "Thu, 4 May 2017 13:46:57 -0500")
Larry Finger <Larry.Finger@lwfinger.net> writes:
> The btcoex code uses #if constructs to compile conditional code. There
> is no way to modify this behavior without editting the source. This
> logic is converted into regular if statements that interrogate a
> boolean variable in a structure known to all routines.
Well technically these are still dead code as there's no way to enable
those. But this is much better than before, now at least we can compile
test the whole code. So thanks for fixing it.
> The new form does not provide any mechanism for dynamic changes, but
> it now is in a form whereby module parameters could be added to select
> the behavior at module load time. In these patches, a number of
> routines removed because they were not referenced must be restored.
We should keep the number of module parameters as low as possible. If
I'm understanding correctly changing the behaviour is needed for testing
purposes? In that case I suspect that debugfs would be more approriate
interface to enable these.
--
Kalle Valo
prev parent reply other threads:[~2017-05-11 11:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 18:46 [PATCH v2 0/4] rtlwifi: btcoex: Remove all references to BT_AUTO_REPORT_ONLY* parameters Larry Finger
2017-05-04 18:46 ` [PATCH v2 1/4] rtlwifi: btcoex: Remove 21a 1ant configuration parameter Larry Finger
2017-05-18 14:07 ` [v2, " Kalle Valo
2017-05-04 18:46 ` [PATCH v2 2/4] rtlwifi: btcoex: Remove 23b " Larry Finger
2017-05-04 18:47 ` [PATCH v2 3/4] rtlwifi: btcoex: Remove 23b 2ant " Larry Finger
2017-05-04 18:47 ` [PATCH v2 4/4] rtlwifi: btcoex: Remove 92e " Larry Finger
2017-05-11 11:46 ` Kalle Valo [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=87a86jvcnp.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=Larry.Finger@lwfinger.net \
--cc=birming@realtek.com \
--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).