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>,
Larry Finger <Larry.Finger@lwfinger.net>,
Ping-Ke Shih <pkshih@realtek.com>,
Birming Chiu <birming@realtek.com>, Shaofu <shaofu@realtek.com>,
Steven Ting <steventing@realtek.com>
Subject: Re: [v2,1/9] rtlwifi: btcoex: add macros to check chip type
Date: Tue, 13 Jun 2017 07:03:17 +0000 (UTC) [thread overview]
Message-ID: <20170613070317.10B13607E8@smtp.codeaurora.org> (raw)
In-Reply-To: <20170605152959.27439-2-Larry.Finger@lwfinger.net>
Larry Finger <Larry.Finger@lwfinger.net> wrote:
> From: Yan-Hsuan Chuang <yhchuang@realtek.com>
>
> For some external functions that have hardware dependency, we need to
> know the type of the hardware before invoking them.
>
> Signed-off-by: Yan-Hsuan Chuang <yhchuang@realtek.com>
> Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
> Cc: Ping-Ke Shih <pkshih@realtek.com>
> Cc: Birming Chiu <birming@realtek.com>
> Cc: Shaofu <shaofu@realtek.com>
> Cc: Steven Ting <steventing@realtek.com>
9 patches applied to wireless-drivers-next.git, thanks.
d178b1321e49 rtlwifi: btcoex: add macros to check chip type
753c953bae5d rtlwifi: btcoex: rename ex_halbtc*ant to ex_btc*ant
6fbbc82adfb2 rtlwifi: btcoex: settings before firmware is downloaded
86f9ab2ef4bd rtlwifi: btcoex: hook external PnP notify by chip for wifi driver
60f44100eee7 rtlwifi: btcoex: add settings before the hardware is ready
7937f02d1953 rtlwifi: btcoex: hook external functions for newer chips
0199103ea7ec rtlwifi: btcoex: bind BT coex information with wifi driver
6aafa2307414 rtlwifi: btcoex: remove unused display functions
c42ea613353c rtlwifi: btcoex: let btcoex get wifi rssi and link status
--
https://patchwork.kernel.org/patch/9766361/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2017-06-13 7:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 15:29 [PATCH v2 0/9] rtlwifi: btcoex: Further updates Larry Finger
2017-06-05 15:29 ` [PATCH v2 1/9] rtlwifi: btcoex: add macros to check chip type Larry Finger
2017-06-13 7:03 ` Kalle Valo [this message]
2017-06-05 15:29 ` [PATCH v2 2/9] rtlwifi: btcoex: rename ex_halbtc*ant to ex_btc*ant Larry Finger
2017-06-05 15:29 ` [PATCH v2 3/9] rtlwifi: btcoex: settings before firmware is downloaded Larry Finger
2017-06-05 15:29 ` [PATCH v2 4/9] rtlwifi: btcoex: hook external PnP notify by chip for wifi driver Larry Finger
2017-06-05 15:29 ` [PATCH v2 5/9] rtlwifi: btcoex: add settings before the hardware is ready Larry Finger
2017-06-05 15:29 ` [PATCH v2 6/9] rtlwifi: btcoex: hook external functions for newer chips Larry Finger
2017-06-05 15:29 ` [PATCH v2 7/9] rtlwifi: btcoex: bind BT coex information with wifi driver Larry Finger
2017-06-05 15:29 ` [PATCH v2 8/9] rtlwifi: btcoex: remove unused display functions Larry Finger
2017-06-05 15:29 ` [PATCH v2 9/9] rtlwifi: btcoex: let btcoex get wifi rssi and link status 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=20170613070317.10B13607E8@smtp.codeaurora.org \
--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).