On 3/12/19 6:46 PM, Dan Murphy wrote:
On 3/12/19 12:28 PM, Jacek Anaszewski wrote:
Hi Dan,
On 3/12/19 6:15 PM, Dan Murphy wrote:
On 3/10/19 1:28 PM, Jacek Anaszewski wrote:
Add public led_compose_name() API for composing LED class device
name basing on fwnode_handle data. The function
On 3/12/19 12:28 PM, Jacek Anaszewski wrote:
> Hi Dan,
>
> On 3/12/19 6:15 PM, Dan Murphy wrote:
>> On 3/10/19 1:28 PM, Jacek Anaszewski wrote:
>>> Add public led_compose_name() API for composing LED class device
>>> name basing on fwnode_handle data. The function composes device name
>>>
On 3/10/19 1:28 PM, Jacek Anaszewski wrote:
> Add public led_compose_name() API for composing LED class device
> name basing on fwnode_handle data. The function composes device name
> according to either a new pattern or the legacy
> pattern. The decision on using the
> particular pattern is
Hi Dan,
On 3/12/19 6:15 PM, Dan Murphy wrote:
On 3/10/19 1:28 PM, Jacek Anaszewski wrote:
Add public led_compose_name() API for composing LED class device
name basing on fwnode_handle data. The function composes device name
according to either a new pattern or the legacy
pattern. The
Two auto corrections:
On 3/10/19 7:28 PM, Jacek Anaszewski wrote:
Add public led_compose_name() API for composing LED class device
name basing on fwnode_handle data. The function composes device name
according to either a new pattern or the legacy
pattern. The decision on using the
particular
Add public led_compose_name() API for composing LED class device
name basing on fwnode_handle data. The function composes device name
according to either a new pattern or the legacy
pattern. The decision on using the
particular pattern is made basing on whether fwnode contains new
"function" and
6 matches
Mail list logo