From: Hauke Mehrtens <hauke@hauke-m.de>
To: Johannes Berg <johannes@sipsolutions.net>, Luca Coelho <luca@coelho.fi>
Cc: backports@vger.kernel.org
Subject: iwlwifi build problem in backports 5.5
Date: Mon, 23 Dec 2019 19:58:45 +0100 [thread overview]
Message-ID: <ca1799cd-c802-83db-42b2-e51084f57f9b@hauke-m.de> (raw)
Hi Johannes and Luca,
I see this build problem in backports based on kernel 5.5:
---------------------------------------------------------------
drivers/net/wireless/intel/iwlwifi/pcie/rx.c: In function
‘iwl_pcie_rx_handle’:
drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1532:11: error: ‘struct
napi_struct’ has no member named ‘rx_count’
if (napi->rx_count) {
^~
drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1533:34: error: ‘struct
napi_struct’ has no member named ‘rx_list’; did you mean ‘dev_list’?
netif_receive_skb_list(&napi->rx_list);
^~~~~~~
dev_list
drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1534:26: error: ‘struct
napi_struct’ has no member named ‘rx_list’; did you mean ‘dev_list’?
INIT_LIST_HEAD(&napi->rx_list);
^~~~~~~
dev_list
drivers/net/wireless/intel/iwlwifi/pcie/rx.c:1535:8: error: ‘struct
napi_struct’ has no member named ‘rx_count’
napi->rx_count = 0;
^~
make[10]: ***
[/usr/src/linux-headers-4.19.0-6-common/scripts/Makefile.build:308:
drivers/net/wireless/intel/iwlwifi/pcie/rx.o] Error 1
make[10]: *** Waiting for unfinished jobs....
-----------------------------------------------------------------
This commit in iwlwifi causes the problems:
https://git.kernel.org/linus/b167191e2a851cb2e4c6ef8b91c83ff73ef41872
it depends on this change:
https://git.kernel.org/linus/323ebb61e32b478e2432c5a3cbf9e2ca678a9609
Hauke
--
To unsubscribe from this list: send the line "unsubscribe backports" in
reply other threads:[~2019-12-23 18:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ca1799cd-c802-83db-42b2-e51084f57f9b@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=backports@vger.kernel.org \
--cc=johannes@sipsolutions.net \
--cc=luca@coelho.fi \
/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).