[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221020032340.5cf101c0@canb.auug.org.au>
Date: Thu, 20 Oct 2022 03:23:40 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Kalle Valo <kvalo@...nel.org>,
Johannes Berg <johannes@...solutions.net>,
Wireless <linux-wireless@...r.kernel.org>
Cc: David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Ilan Peer <ilan.peer@...el.com>,
Johannes Berg <johannes.berg@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: linux-next: manual merge of the wireless-next tree with Linus' tree
Hi all,
FIXME: Add owner of second tree to To:
Add author(s)/SOB of conflicting commits.
Today's linux-next merge of the wireless-next tree got a conflict in:
net/mac80211/util.c
between commit:
ff05d4b45dd8 ("wifi: mac80211: fix MBSSID parsing use-after-free")
from the origin tree and commit:
ff05d4b45dd8 ("wifi: mac80211: fix MBSSID parsing use-after-free")
from the wireless-next tree.
I fixed it up (I just used the latter version) 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
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists