On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
> 1. Rename max77693_led_platform_data to max77693_led_config_data to
>avoid making impression that the led driver expects a board file -
>it relies on Device Tree data.
> 2. Remove fleds array, as the DT binding design has changed
> 3. Add
On Fri, 09 Jan 2015, Jacek Anaszewski wrote:
1. Rename max77693_led_platform_data to max77693_led_config_data to
avoid making impression that the led driver expects a board file -
it relies on Device Tree data.
2. Remove fleds array, as the DT binding design has changed
3. Add label
On Fri 2015-01-09 16:22:56, Jacek Anaszewski wrote:
> 1. Rename max77693_led_platform_data to max77693_led_config_data to
>avoid making impression that the led driver expects a board file -
>it relies on Device Tree data.
> 2. Remove fleds array, as the DT binding design has changed
> 3.
1. Rename max77693_led_platform_data to max77693_led_config_data to
avoid making impression that the led driver expects a board file -
it relies on Device Tree data.
2. Remove fleds array, as the DT binding design has changed
3. Add "label" array for Device Tree strings with the name of a
1. Rename max77693_led_platform_data to max77693_led_config_data to
avoid making impression that the led driver expects a board file -
it relies on Device Tree data.
2. Remove fleds array, as the DT binding design has changed
3. Add label array for Device Tree strings with the name of a LED
On Fri 2015-01-09 16:22:56, Jacek Anaszewski wrote:
1. Rename max77693_led_platform_data to max77693_led_config_data to
avoid making impression that the led driver expects a board file -
it relies on Device Tree data.
2. Remove fleds array, as the DT binding design has changed
3. Add
6 matches
Mail list logo
