Re: [PATCH] coresight: Use local coresight_desc instances

On 13/07/16 17:21, kbuild test robot wrote: Hi, [auto build test ERROR on next-20160712] [cannot apply to v4.7-rc7 v4.7-rc6 v4.7-rc5 v4.7-rc7] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] coresight: Use local coresight_desc instances

On 13/07/16 17:21, kbuild test robot wrote: Hi, [auto build test ERROR on next-20160712] [cannot apply to v4.7-rc7 v4.7-rc6 v4.7-rc5 v4.7-rc7] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] coresight: Use local coresight_desc instances

Hi, [auto build test ERROR on next-20160712] [cannot apply to v4.7-rc7 v4.7-rc6 v4.7-rc5 v4.7-rc7] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] coresight: Use local coresight_desc instances

Hi, [auto build test ERROR on next-20160712] [cannot apply to v4.7-rc7 v4.7-rc6 v4.7-rc5 v4.7-rc7] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH] coresight: Use local coresight_desc instances

Each coresight device prepares a description for coresight_register() in struct coresight_desc. Once we register the device, the description is useless and can be freed. The coresight_desc is small enough (48bytes on 64bit) to be allocated on the stack. Hence use an automatic variable to avoid a

[PATCH] coresight: Use local coresight_desc instances

Each coresight device prepares a description for coresight_register() in struct coresight_desc. Once we register the device, the description is useless and can be freed. The coresight_desc is small enough (48bytes on 64bit) to be allocated on the stack. Hence use an automatic variable to avoid a