From: Johannes Berg <johannes@sipsolutions.net>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: backports@vger.kernel.org, john@phrozen.org
Subject: Re: [PATCH 04/10] dependencies: Make RSI_COEX coexistence depend on kernel >= 4.17
Date: Sun, 23 Sep 2018 22:20:32 +0200 [thread overview]
Message-ID: <1537734032.1707.13.camel@sipsolutions.net> (raw)
In-Reply-To: <20180923174535.16198-5-hauke@hauke-m.de> (sfid-20180923_194549_145993_73713907)
On Sun, 2018-09-23 at 19:45 +0200, Hauke Mehrtens wrote:
> When RSI_COEX is activated the driver wants to link against the
> rsi_bt_ops symbol from the bluetooth driver btrsi. This driver was only
> added in kernel 4.17. Deactivate bluetooth coexistence support for older
> kernel versions.
>
> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
> ---
> dependencies | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/dependencies b/dependencies
> index 74f8a80f..555f31fb 100644
> --- a/dependencies
> +++ b/dependencies
> @@ -53,6 +53,9 @@ USB_NET_RNDIS_WLAN 4.6
> # depends on struct mmc_card::ocr
> RSI_SDIO 3.13
>
> +# For Coexsitence the BT driver has to export rsi_bt_ops
Typo :)
But I guess I can fix it - I won't apply right now (need to sleep) but
hopefully tomorrow (though I'll probably have power cut some time during
the day, so who knows what'll happen)
johannes
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2018-09-24 2:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 17:45 [PATCH 00/10] backports: misc fixes to improve support of 4.19 Hauke Mehrtens
2018-09-23 17:45 ` [PATCH 01/10] backports: Remove ssb and bcma Hauke Mehrtens
2018-09-23 20:10 ` Johannes Berg
2018-09-23 20:18 ` Hauke Mehrtens
2018-09-24 10:48 ` Johannes Berg
2018-09-24 20:17 ` Hauke Mehrtens
2018-09-23 17:45 ` [PATCH 02/10] backports: Remove NFC support Hauke Mehrtens
2018-09-23 17:45 ` [PATCH 03/10] copy: Add crc32poly.h Hauke Mehrtens
2018-09-23 17:45 ` [PATCH 04/10] dependencies: Make RSI_COEX coexistence depend on kernel >= 4.17 Hauke Mehrtens
2018-09-23 20:20 ` Johannes Berg [this message]
2018-09-23 17:45 ` [PATCH 05/10] dependencies: Make WIL6210 depend on kernel >= 4.8 Hauke Mehrtens
2018-09-23 20:12 ` Johannes Berg
2018-09-23 20:36 ` Hauke Mehrtens
2018-09-23 17:45 ` [PATCH 06/10] dependencies: make hostap and atmel depend on kernel >= 4.18 Hauke Mehrtens
2018-09-23 20:17 ` Johannes Berg
2018-09-23 20:23 ` Hauke Mehrtens
2018-09-23 20:33 ` Johannes Berg
2018-09-23 17:45 ` [PATCH 07/10] patches: make mt76 use skb_pad() instead of __skb_pad() Hauke Mehrtens
2018-09-23 17:45 ` [PATCH 08/10] patches: remove .coredump from struct driver for kernel < 4.16 Hauke Mehrtens
2018-09-24 8:36 ` Johannes Berg
2018-09-24 20:20 ` Hauke Mehrtens
2018-09-23 17:45 ` [PATCH 09/10] backports: Make netdev destructor spatch apply correctly again Hauke Mehrtens
2018-09-23 20:17 ` Johannes Berg
2018-09-23 17:45 ` [PATCH 10/10] patches: Do not remove linux/kmemleak.h include Hauke Mehrtens
2018-09-23 20:18 ` Johannes Berg
2018-09-24 8:12 ` [PATCH 00/10] backports: misc fixes to improve support of 4.19 Johannes Berg
2018-09-24 20:27 ` Hauke Mehrtens
2018-09-24 20:28 ` Johannes Berg
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=1537734032.1707.13.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=backports@vger.kernel.org \
--cc=hauke@hauke-m.de \
--cc=john@phrozen.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).