Re: [PATCH v5] mfd: tps6105x: Fix possible NULL pointer access.

2015-09-25 Thread Lee Jones
On Fri, 25 Sep 2015, Grigoryev Denis wrote: > tps6105 driver provides two cells. One is for GPIO and another one is > for selected mode depending on platform data. When tps6105x is used in > GPIO-only mode, this driver calls mfd_add_devices() with mfd_cell > .name == NULL. This value causes an

[PATCH v5] mfd: tps6105x: Fix possible NULL pointer access.

2015-09-25 Thread Grigoryev Denis
tps6105 driver provides two cells. One is for GPIO and another one is for selected mode depending on platform data. When tps6105x is used in GPIO-only mode, this driver calls mfd_add_devices() with mfd_cell .name == NULL. This value causes an oops in platform_device_register() later. The

[PATCH v5] mfd: tps6105x: Fix possible NULL pointer access.

2015-09-25 Thread Grigoryev Denis
tps6105 driver provides two cells. One is for GPIO and another one is for selected mode depending on platform data. When tps6105x is used in GPIO-only mode, this driver calls mfd_add_devices() with mfd_cell .name == NULL. This value causes an oops in platform_device_register() later. The

Re: [PATCH v5] mfd: tps6105x: Fix possible NULL pointer access.

2015-09-25 Thread Lee Jones
On Fri, 25 Sep 2015, Grigoryev Denis wrote: > tps6105 driver provides two cells. One is for GPIO and another one is > for selected mode depending on platform data. When tps6105x is used in > GPIO-only mode, this driver calls mfd_add_devices() with mfd_cell > .name == NULL. This value causes an