| 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
| ||
|
Date: Mon, 07 Oct 2013 11:09:00 -0500 From: Larry Finger <Larry.Finger@...inger.net> To: Joe Perches <joe@...ches.com> CC: Thierry Reding <thierry.reding@...il.com>, "John W. Linville" <linville@...driver.com>, Arend van Spriel <arend@...adcom.com>, linux-next@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: linux-next: manual merge of the wireless-next tree On 10/07/2013 10:56 AM, Joe Perches wrote: > On Mon, 2013-10-07 at 10:48 -0500, Larry Finger wrote: >> On 10/07/2013 10:18 AM, Thierry Reding wrote: >>> Today's linux-next merge of the wireless-next tree got conflicts in: >>> >>> drivers/net/wireless/brcm80211/brcmfmac/dhd_bus.h >>> drivers/net/wireless/rtlwifi/rtl8188ee/phy.h >>> drivers/net/wireless/rtlwifi/rtl8192ce/phy.h >>> drivers/net/wireless/rtlwifi/rtl8192de/phy.h >>> drivers/net/wireless/rtlwifi/rtl8723ae/phy.h > [] >> Yes, the patches for rtlwifi problems are correct. All of these problems would >> have been avoided if changes to wireless drivers were sent to the wireless tree >> rather than direct submission to net-next!!!! > > They were and you acked it. > https://lkml.org/lkml/2013/9/25/589 > > Who picks it up first and applies it is > not in my domain. Fair enough. I should have asked DaveM to let John apply those changes. Larry -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists