linux-kernel - Re: linux-next: manual merge of the wireless-drivers-next 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 for Android: free password hash cracker in your pocket

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

Date:   Fri, 21 Aug 2020 01:58:56 -0500
From:   "Gustavo A. R. Silva" <gustavo@...eddedor.com>
To:     Kalle Valo <kvalo@...eaurora.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Wireless <linux-wireless@...r.kernel.org>,
        "Gustavo A. R. Silva" <gustavoars@...nel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: manual merge of the wireless-drivers-next tree with
 the kspp-gustavo tree

Hi Kalle,

On 8/19/20 01:26, Kalle Valo wrote:
> Stephen Rothwell <sfr@...b.auug.org.au> writes:
> 
>> Today's linux-next merge of the wireless-drivers-next tree got a
>> conflict in:
>>
>>   drivers/net/wireless/ath/ath11k/dp_rx.c
>>
>> between commit:
>>
>>   58e813cceabd ("treewide: Use fallthrough pseudo-keyword")
>>
>> from the kspp-gustavo tree and commit:
>>
>>   0b294aebb6a0 ("ath11k: Use fallthrough pseudo-keyword")
>>
>> from the wireless-drivers-next tree.
>>
>> I fixed it up (the latter removed an extra blank line) 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.
> 
> Gustavo, why do you have patches changing ath11k in your tree? PLEASE
> don't do that! Instead properly send them to linux-wireless and ath11k
> lists, as you have done before. That way there are no unncessary
> conflicts like this one which cause extra work for the maintainers.
> 

Sure thing. Sorry about that. I just sent out some patches to address the
vast majority of the remaining fall-through conversions to make in
drivers/net/wireless/

Thanks
--
Gustavo