linux-kernel - Re: [PATCH v2 06/27] brcm80211: move under broadcom vendor directory

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5652EA61.1080103@broadcom.com>
Date:	Mon, 23 Nov 2015 11:28:49 +0100
From:	Arend van Spriel <arend@...adcom.com>
To:	Kalle Valo <kvalo@...eaurora.org>
CC:	Hauke Mehrtens <hauke@...ke-m.de>,
	<linux-wireless@...r.kernel.org>, <netdev@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <brcm80211-dev-list@...adcom.com>
Subject: Re: [PATCH v2 06/27] brcm80211: move under broadcom vendor directory

On 11/22/2015 06:23 PM, Kalle Valo wrote:
> Arend van Spriel <arend@...adcom.com> writes:
>
>> On 11/19/2015 08:48 AM, Kalle Valo wrote:
>>> Hauke Mehrtens <hauke@...ke-m.de> writes:
>>>
>>>> On 11/18/2015 03:45 PM, Kalle Valo wrote:
>>>>> Part of reorganising wireless drivers directory and Kconfig. Note that I had to
>>>>> edit Makefiles from subdirectories to use the new location.
>>>>>
>>>>> Signed-off-by: Kalle Valo <kvalo@...eaurora.org>
>>>>> ---
>>>>
>>>> I would prefer to remove the brcm80211 directory in this process and create:
>>>> drivers/net/wireless/broadcom/brcmfmac
>>>> drivers/net/wireless/broadcom/brcmsmac
>>>> drivers/net/wireless/broadcom/brcmutil
>>>> drivers/net/wireless/broadcom/include
>>>>
>>>> This way we have one directory less.
>>>
>>> I think this could be done separately. This patchset is big enough
>>> already, I would not like to make it anymore complicated.
>>>
>>> And I actually like the brcm80211 directory, I would not mind keeping it
>>> still.
>>
>> I prefer to keep it as brcmsmac and brcmfmac rely on brcmutil module
>> so I want to keep them together under brcm80211.
>>
>> So does this patch go in before or after the patches I submitted
>> before the merge window. I hope after :-p
>
> Sorry, the vendor patches go in first :) It's much safer that way.
>
> But I think that git should be smart enough and your patchset from
> before the merge window should still apply without issues.

Will see if that is true when I merge it in our internal repo. :-p

Thanks,
Arend

--
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/