[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190409110607.29df3cf3@canb.auug.org.au>
Date: Tue, 9 Apr 2019 11:06:07 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Johannes Berg <johannes@...solutions.net>,
Wireless <linux-wireless@...r.kernel.org>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Felix Fietkau <nbd@....name>
Subject: linux-next: manual merge of the mac80211-next tree with the
mac80211 tree
Hi all,
Today's linux-next merge of the mac80211-next tree got a conflict in:
net/mac80211/tx.c
between commit:
eb9b64e3a9f8 ("mac80211: fix memory accounting with A-MSDU aggregation")
from the mac80211 tree and commit:
dcec1d9bc8a7 ("mac80211: calculate hash for fq without holding fq->lock in itxq enqueue")
from the mac80211-next tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc net/mac80211/tx.c
index 2e816dd67be7,3655aae96df1..000000000000
--- a/net/mac80211/tx.c
+++ b/net/mac80211/tx.c
@@@ -3221,7 -3219,7 +3219,8 @@@ static bool ieee80211_amsdu_aggregate(s
u8 max_subframes = sta->sta.max_amsdu_subframes;
int max_frags = local->hw.max_tx_fragments;
int max_amsdu_len = sta->sta.max_amsdu_len;
+ int orig_truesize;
+ u32 flow_idx;
__be16 len;
void *data;
bool ret = false;
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists