On Thu, Jan 18, 2018 at 06:02:44PM +0000, York Sun wrote:
On 01/18/2018 09:59 AM, Tom Rini wrote:
On Thu, Jan 18, 2018 at 05:25:01PM +0000, York Sun wrote:
Tom and Wolfgang,
Do we have guideline on dual licensing the code in U-Boot? If I collect consent from all contributors and copyright holders to a particular file, am I able to re-license the file? If yes, how to determine the list of contributors?
In general, I think you would use 'git log' to see who contributed to a given file, and make sure that everyone who authored a change signed off on the license change.
Thanks.
With regards to dts files, this is another reason I would like to see that done as a strict re-sync with Linux rather than a stand-alone change. Saying we're importing file X from the kernel at revision Y makes the license change pretty easy to spot and justify.
For the dts files, they already exist in U-Boot. Can the team still say "importing" from Linux? The files in U-Boot is only a small subset of those in Linux.
Yes, if it's a strict replace file A with contents of the same file from Linux, it's re-importing. I thought these boards had already re-synced before but perhaps not? It's something we do from time to time on other platforms.