linux-kernel - linux-next: manual merge of the staging tree with the kspp-gustavo tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 17 Feb 2022 14:16:03 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Greg KH <greg@...ah.com>,
        "Gustavo A. R. Silva" <gustavo@...eddedor.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Gustavo A. R. Silva" <gustavoars@...nel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Michael Straube <straube.linux@...il.com>
Subject: linux-next: manual merge of the staging tree with the kspp-gustavo
 tree

Hi all,

Today's linux-next merge of the staging tree got a conflict in:

  drivers/staging/r8188eu/include/ieee80211.h

between commit:

  fbe9ccfe809d ("treewide: Replace zero-length arrays with flexible-array members")

from the kspp-gustavo tree and commit:

  6c36bcbfcef7 ("staging: r8188eu: remove unused structs from ieee80211.h")

from the staging tree.

I fixed it up (the latter removed the structs updated by the former) 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