Re: [PATCH v3] misc: sram-exec: Use aligned fncpy instead of memcpy

2017-06-15 Thread Florian Fainelli
On 05/18/2017 08:07 AM, Dave Gerlach wrote: > Currently the sram-exec functionality, which allows allocation of > executable memory and provides an API to move code to it, is only > selected in configs for the ARM architecture. Based on commit > 5756e9dd0de6 ("ARM: 6640/1: Thumb-2: Symbol

Re: [PATCH v3] misc: sram-exec: Use aligned fncpy instead of memcpy

2017-06-15 Thread Florian Fainelli
On 05/18/2017 08:07 AM, Dave Gerlach wrote: > Currently the sram-exec functionality, which allows allocation of > executable memory and provides an API to move code to it, is only > selected in configs for the ARM architecture. Based on commit > 5756e9dd0de6 ("ARM: 6640/1: Thumb-2: Symbol

[PATCH v3] misc: sram-exec: Use aligned fncpy instead of memcpy

2017-05-18 Thread Dave Gerlach
Currently the sram-exec functionality, which allows allocation of executable memory and provides an API to move code to it, is only selected in configs for the ARM architecture. Based on commit 5756e9dd0de6 ("ARM: 6640/1: Thumb-2: Symbol manipulation macros for function body copying") simply

[PATCH v3] misc: sram-exec: Use aligned fncpy instead of memcpy

2017-05-18 Thread Dave Gerlach
Currently the sram-exec functionality, which allows allocation of executable memory and provides an API to move code to it, is only selected in configs for the ARM architecture. Based on commit 5756e9dd0de6 ("ARM: 6640/1: Thumb-2: Symbol manipulation macros for function body copying") simply