Re: [PATCH] pinctrl-exynos5440: Use off-stack memory for pinctrl_gpio_range

On 04/19/2016 09:24 AM, Tomasz Figa wrote: > Hi Andrew, > > 2016-04-19 13:13 GMT+09:00 Andrew Jeffery : >> The range is registered into a linked list which can be referenced >> throughout the lifetime of the driver. Ensure the range's memory is useful >> for the same lifetime by

Re: [PATCH] pinctrl-exynos5440: Use off-stack memory for pinctrl_gpio_range

On 04/19/2016 09:24 AM, Tomasz Figa wrote: > Hi Andrew, > > 2016-04-19 13:13 GMT+09:00 Andrew Jeffery : >> The range is registered into a linked list which can be referenced >> throughout the lifetime of the driver. Ensure the range's memory is useful >> for the same lifetime by adding it to the

Re: [PATCH] pinctrl-exynos5440: Use off-stack memory for pinctrl_gpio_range

Hi Andrew, 2016-04-19 13:13 GMT+09:00 Andrew Jeffery : > The range is registered into a linked list which can be referenced > throughout the lifetime of the driver. Ensure the range's memory is useful > for the same lifetime by adding it to the driver's private data structure. >

Re: [PATCH] pinctrl-exynos5440: Use off-stack memory for pinctrl_gpio_range

Hi Andrew, 2016-04-19 13:13 GMT+09:00 Andrew Jeffery : > The range is registered into a linked list which can be referenced > throughout the lifetime of the driver. Ensure the range's memory is useful > for the same lifetime by adding it to the driver's private data structure. > > The bug was

[PATCH] pinctrl-exynos5440: Use off-stack memory for pinctrl_gpio_range

The range is registered into a linked list which can be referenced throughout the lifetime of the driver. Ensure the range's memory is useful for the same lifetime by adding it to the driver's private data structure. The bug was introduced in the driver's initial commit, which was present in

[PATCH] pinctrl-exynos5440: Use off-stack memory for pinctrl_gpio_range

The range is registered into a linked list which can be referenced throughout the lifetime of the driver. Ensure the range's memory is useful for the same lifetime by adding it to the driver's private data structure. The bug was introduced in the driver's initial commit, which was present in