Re: [dunfell/master PATCH V4] trusted-firmware-a: Update to v2.4 merge

["Denys Dmytriyenko" <denis@denix.org>]

On Thu, Dec 10, 2020 at 06:04:18PM -0600, Nishanth Menon wrote:
> On 19:00-20201210, Denys Dmytriyenko wrote:
> > On Thu, Dec 10, 2020 at 05:49:57PM -0600, Nishanth Menon wrote:
> > > Update to v2.4 tag merge from upstream to keep TF-A in sync.
> > > 
> > > For major changes in trusted-firmware-a, See:
> > > https://trustedfirmware-a.readthedocs.io/en/latest/change-log.html#version-2-4
> > > 
> > > TI specific fixups include:
> > >  - stub for shutdown (CPUs enter wfi)
> > >  - uart console is now configurable.
> > > 
> > > While at it, update to include PV_k3 as 2.4 and provide the license file
> > > checksum.
> > > 
> > > NOTE: We use PV_k3 instead of PV since this allows meta-ti to not
> > > affect other platforms esp in a multi-BSP configuration.
> > > 
> > > Suggested-by: Dan Murphy <dmurphy@ti.com>
> > > Signed-off-by: Nishanth Menon <nm@ti.com>
> > 
> > Reviewed-by: Denys Dmytriyenko <denis@denix.org>
> > 
> > Nice-to-have would be to explain the license checksum change and whether it 
> > affects the actual license. The checksum there is specifically to catch any 
> > changes to the license file and prevent re-licensing to pass unnoticed...
> > 
> 
> Hmm.. good idea.. but it was'nt present before.. so i could state
> something as follows in the commit message:
> 
> ----
> 
> While at it, update to include PV_k3 as 2.4. We use PV_k3 instead of
> PV since this allows meta-ti to not affect other platforms esp in a
> multi-BSP configuration.
> 
> We also add LIC_FILES_CHKSUM_k3 to make sure that we don't let any
> re-licensing in the project pass through unnoticed as that has to
> be carefully examined for making sure we have all the right legal
> compliance.

Right, but you don't explain what actually changed to cause the checksum 
update...

E.g.: "checksum changed due to upstream commit XYZ to update the year, the 
license itself is the same" or "checksum changed due to addition on SPDX 
header in commit XYZ, no license change"

But you need to examine it yourself. Otherwise it could be: "the license has 
changed from GPLv2 to GPLv3" and also update the actual LICENSE_k3 variable.


> ----
> 
> If good, I can repost with your reviewed-by plucked up..
> 
> -- 
> Regards,
> Nishanth Menon
> Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D
> 

-- 
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186  6D76 4209 0272 9A92 C964