Re: [PATCH v8 0/5] firmware: add driver data API

2017-06-05 Thread Luis R. Rodriguez
On Fri, May 19, 2017 at 12:10:35PM -0700, Luis R. Rodriguez wrote: > Greg, > > Even though using copyleft-next was fine by Linus [0], AKASHI had brought that > he expected to see an "or" clause on the license declarations when using > copyleft-next. This was the only pending issue from the last

Re: [PATCH v8 0/5] firmware: add driver data API

2017-06-05 Thread Luis R. Rodriguez
On Fri, May 19, 2017 at 12:10:35PM -0700, Luis R. Rodriguez wrote: > Greg, > > Even though using copyleft-next was fine by Linus [0], AKASHI had brought that > he expected to see an "or" clause on the license declarations when using > copyleft-next. This was the only pending issue from the last

[PATCH v8 0/5] firmware: add driver data API

2017-05-19 Thread Luis R. Rodriguez
Greg, Even though using copyleft-next was fine by Linus [0], AKASHI had brought that he expected to see an "or" clause on the license declarations when using copyleft-next. This was the only pending issue from the last v7 series [1]. To be safe I re-touched the subject and Alan and Ted brought up

[PATCH v8 0/5] firmware: add driver data API

2017-05-19 Thread Luis R. Rodriguez
Greg, Even though using copyleft-next was fine by Linus [0], AKASHI had brought that he expected to see an "or" clause on the license declarations when using copyleft-next. This was the only pending issue from the last v7 series [1]. To be safe I re-touched the subject and Alan and Ted brought up