On 23-2-2017 22:41, Rafał Miłecki wrote:
> Hey Arend,
>
> On 8 February 2017 at 10:54, Arend Van Spriel
> wrote:
>> On 2-2-2017 22:33, Rafał Miłecki wrote:
>>> From: Rafał Miłecki
>>>
>>> This will allow getting struct device reference from the
Hey Arend,
On 8 February 2017 at 10:54, Arend Van Spriel
wrote:
> On 2-2-2017 22:33, Rafał Miłecki wrote:
>> From: Rafał Miłecki
>>
>> This will allow getting struct device reference from the passed
>> brcmf_pub for the needs of dev_err. More
On 8 February 2017 at 10:54, Arend Van Spriel
wrote:
> On 2-2-2017 22:33, Rafał Miłecki wrote:
>> From: Rafał Miłecki
>>
>> This will allow getting struct device reference from the passed
>> brcmf_pub for the needs of dev_err. More detailed
On 2017-02-08 15:52, Kalle Valo wrote:
Rafał Miłecki writes:
On 2017-02-08 10:54, Arend Van Spriel wrote:
On 2-2-2017 22:33, Rafał Miłecki wrote:
From: Rafał Miłecki
This will allow getting struct device reference from the passed
brcmf_pub for the needs
On 2017-02-08 10:54, Arend Van Spriel wrote:
On 2-2-2017 22:33, Rafał Miłecki wrote:
From: Rafał Miłecki
This will allow getting struct device reference from the passed
brcmf_pub for the needs of dev_err. More detailed messages are really
important for home routers which
On 2-2-2017 22:33, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> This will allow getting struct device reference from the passed
> brcmf_pub for the needs of dev_err. More detailed messages are really
> important for home routers which frequently have 2 (or even 3) wireless
>
From: Rafał Miłecki
This will allow getting struct device reference from the passed
brcmf_pub for the needs of dev_err. More detailed messages are really
important for home routers which frequently have 2 (or even 3) wireless
cards supported by brcmfmac.
Note that all calls