On 7-3-2017 10:44, Kalle Valo wrote:
> Arnd Bergmann writes:
>
>> On Mon, Mar 6, 2017 at 5:19 PM, Kalle Valo wrote:
>>> Arend Van Spriel writes:
>>>
On 2-3-2017 17:38, Arnd Bergmann wrote:
> With KASAN and a couple of other patches applied, this driver is one
> of the few remaining
Arnd Bergmann writes:
> On Mon, Mar 6, 2017 at 5:19 PM, Kalle Valo wrote:
>> Arend Van Spriel writes:
>>
>>> On 2-3-2017 17:38, Arnd Bergmann wrote:
With KASAN and a couple of other patches applied, this driver is one
of the few remaining ones that actually use more than 2048 bytes of
On Mon, Mar 6, 2017 at 5:19 PM, Kalle Valo wrote:
> Arend Van Spriel writes:
>
>> On 2-3-2017 17:38, Arnd Bergmann wrote:
>>> With KASAN and a couple of other patches applied, this driver is one
>>> of the few remaining ones that actually use more than 2048 bytes of
>>> kernel stack:
>>>
>>> broa
Arend Van Spriel writes:
> On 2-3-2017 17:38, Arnd Bergmann wrote:
>> With KASAN and a couple of other patches applied, this driver is one
>> of the few remaining ones that actually use more than 2048 bytes of
>> kernel stack:
>>
>> broadcom/brcm80211/brcmsmac/phy/phy_n.c: In function
>> 'wlc_p
On 2-3-2017 17:38, Arnd Bergmann wrote:
> With KASAN and a couple of other patches applied, this driver is one
> of the few remaining ones that actually use more than 2048 bytes of
> kernel stack:
>
> broadcom/brcm80211/brcmsmac/phy/phy_n.c: In function
> 'wlc_phy_workarounds_nphy_gainctrl':
> br
With KASAN and a couple of other patches applied, this driver is one
of the few remaining ones that actually use more than 2048 bytes of
kernel stack:
broadcom/brcm80211/brcmsmac/phy/phy_n.c: In function
'wlc_phy_workarounds_nphy_gainctrl':
broadcom/brcm80211/brcmsmac/phy/phy_n.c:16065:1: warning
