From: Hauke Mehrtens <hauke@hauke-m.de>
To: backports@vger.kernel.org
Cc: Hauke Mehrtens <hauke@hauke-m.de>
Subject: [PATCH 3/4] backports: Add missing include for brcmfmac
Date: Tue, 26 Mar 2019 16:11:37 +0100 [thread overview]
Message-ID: <20190326151138.4141-3-hauke@hauke-m.de> (raw)
In-Reply-To: <20190326151138.4141-1-hauke@hauke-m.de>
When building against kernel 4.8, 3.14 and older, brcmfmac failed
because struct sk_buff was not declared in brcmfmac/bus.h. This is used
in the brcmf_bus_ops.txdata() callback.
I do not know why this was working before.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
---
patches/0013-fix-makefile-includes/brcmfmac.patch | 13 +++++++++++++
1 file changed, 13 insertions(+)
create mode 100644 patches/0013-fix-makefile-includes/brcmfmac.patch
diff --git a/patches/0013-fix-makefile-includes/brcmfmac.patch b/patches/0013-fix-makefile-includes/brcmfmac.patch
new file mode 100644
index 00000000..9147c80f
--- /dev/null
+++ b/patches/0013-fix-makefile-includes/brcmfmac.patch
@@ -0,0 +1,13 @@
+brcmf_bus_ops.txdata() uses a paramater of type struct sk_buff which
+was not declared here when compiling against kernele 4.8 and older.
+
+--- a/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bus.h
++++ b/drivers/net/wireless/broadcom/brcm80211/brcmfmac/bus.h
+@@ -17,6 +17,7 @@
+ #ifndef BRCMFMAC_BUS_H
+ #define BRCMFMAC_BUS_H
+
++#include <linux/skbuff.h>
+ #include "debug.h"
+
+ /* IDs of the 6 default common rings of msgbuf protocol */
--
2.20.1
--
To unsubscribe from this list: send the line "unsubscribe backports" in
next prev parent reply other threads:[~2019-03-26 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 15:11 [PATCH 1/4] backports: Add rhashtable_lookup_get_insert_fast() Hauke Mehrtens
2019-03-26 15:11 ` [PATCH 2/4] backports: Add smp_acquire__after_ctrl_dep() Hauke Mehrtens
2019-03-26 15:11 ` Hauke Mehrtens [this message]
2019-03-26 15:11 ` [PATCH 4/4] backports: Build CONFIG_MT7603E only for kernel >= 4.2 Hauke Mehrtens
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=20190326151138.4141-3-hauke@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=backports@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.