Re: [PATCH 01/11] brcmfmac: expose device memory to devcoredump subsystem

Arend van Spriel writes: > On 10/14/2015 01:01 PM, Kalle Valo wrote: >> Arend van Spriel writes: >> >>> On 10/12/2015 10:59 AM, Kalle Valo wrote: >>> Arend, are the kbuild errors valid? I would guess they are as wireless-drivers-next should be

Re: [PATCH 01/11] brcmfmac: expose device memory to devcoredump subsystem

Arend van Spriel writes: > On 10/12/2015 10:59 AM, Kalle Valo wrote: >> kbuild test robot writes: >> >>> Hi Arend, >>> >>> [auto build test ERROR on next-20151008 -- if it's inappropriate base, >>> please ignore] >>> >>> config: x86_64-randconfig-x011-201540

Re: [PATCH 01/11] brcmfmac: expose device memory to devcoredump subsystem

On 10/14/2015 01:01 PM, Kalle Valo wrote: Arend van Spriel writes: On 10/12/2015 10:59 AM, Kalle Valo wrote: kbuild test robot writes: Hi Arend, [auto build test ERROR on next-20151008 -- if it's inappropriate base, please ignore] config:

Re: [PATCH 01/11] brcmfmac: expose device memory to devcoredump subsystem

kbuild test robot writes: > Hi Arend, > > [auto build test ERROR on next-20151008 -- if it's inappropriate base, please > ignore] > > config: x86_64-randconfig-x011-201540 (attached as .config) > reproduce: > # save the attached .config to linux build tree > make

Re: [PATCH 01/11] brcmfmac: expose device memory to devcoredump subsystem

On 10/12/2015 10:59 AM, Kalle Valo wrote: kbuild test robot writes: Hi Arend, [auto build test ERROR on next-20151008 -- if it's inappropriate base, please ignore] config: x86_64-randconfig-x011-201540 (attached as .config) reproduce: # save the attached .config to

Re: [PATCH 01/11] brcmfmac: expose device memory to devcoredump subsystem

Hi Arend, [auto build test ERROR on next-20151008 -- if it's inappropriate base, please ignore] config: x86_64-randconfig-x011-201540 (attached as .config) reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All errors (new ones prefixed by >>):

[PATCH 01/11] brcmfmac: expose device memory to devcoredump subsystem

Upon PSM watchdog event received from firmware the driver will obtain a memory snapshot of the device and expose it to user-space through the devcoredump framework. This will trigger a uevent. Reviewed-by: Hante Meuleman Reviewed-by: Franky (Zhenhui) Lin