[meta-freescale] Updates to meta-freescale (master) in 2017-01-24

[Bas Mevissen]

On 24/01/17 15:20, Otavio Salvador wrote:
> On Tue, Jan 24, 2017 at 11:38 AM, Bas Mevissen <abuse at basmevissen.nl> wrote:
>> On 24/01/17 13:19, Otavio Salvador wrote:
>>>
>>> Hello,
>>>
>>> I pushed following updates:
>>>
>>> commit 67b09d4b6bec8efae566d04b24f67af439349452 (HEAD -> master,
>>> yocto/master)
>>> Author: Fabio Berton <fabio.berton at ossystems.com.br>
>>> Date:   Mon Jan 23 17:06:06 2017 -0200
>>>
>>>     linux-fslc-imx: Bump revision to ee67fc7e072d
>>>
>>
>> Will this be merged to Morty as well?
>
> This is intended. We made a morty-next to test this is few more pending changes.
>

Great.

>>>     This commit merge tag Linux 4.1.38 and apply the following changes:
>>>
>>>       - ee67fc7e072d (HEAD -> 4.1-2.0.x-imx, origin/4.1-2.0.x-imx) ARM:
>>>         dts:imx7s-warp: Add watchdog pinmux
>>
>>
>> This seems fine for Morty as well.
>>
>>>       - 5fd79049c122 ARM: dts: imx7: Add "LPSR" to LPSR iomux pin names
>>
>>
>> This is a good idea, however it will break custom DTS files which I think is
>> not acceptable in a stable branch. A solution for Morty would be to have
>> both the new with-LPSR and the current non-LPSR symbols available in
>> imx7d-pinfunc-lpsr.h.
>
> This is not a big problem; anyone using a fork will need to merge this
> change on their tree so this won't propagate for their forks without
> they explicitly doing so. If they are blindly patching this recipe...
> well... then they will need to take care of fixing their bad code ;-)
>

True, but it might a bit harsh. Luckily it is documented now :-)

(having said that, my current development is following morty blindly and 
I haven't had anything broken yet)

>>>       - 739f0c753a6d Merge tag 'v4.1.38' into 4.1-2.0.x-imx
>>>
>> See linux-fslc-imx bump.

Regards,

Bas.