Re: [PATCH v3 0/6] Prerequisites for NXP LS104xA SMMU enablement
From: Andreas FÃrber
Date: Mon Jun 03 2019 - 12:46:06 EST
Am 31.05.19 um 19:32 schrieb Laurentiu Tudor:
>> -----Original Message-----
>> From: Andreas FÃrber <afaerber@xxxxxxx>
>> Sent: Friday, May 31, 2019 8:04 PM
>> Hello Laurentiu,
>> Am 31.05.19 um 18:46 schrieb Laurentiu Tudor:
>>>> -----Original Message-----
>>>> From: Andreas FÃrber <afaerber@xxxxxxx>
>>>> Sent: Friday, May 31, 2019 7:15 PM
>>>> Hi Laurentiu,
>>>> Am 30.05.19 um 16:19 schrieb laurentiu.tudor@xxxxxxx:
>>>>> This patch series contains several fixes in preparation for SMMU
>>>>> support on NXP LS1043A and LS1046A chips. Once these get picked up,
>>>>> I'll submit the actual SMMU enablement patches consisting in the
>>>>> required device tree changes.
>>>> Have you thought through what will happen if this patch ordering is not
>>>> preserved? In particular, a user installing a future U-Boot update with
>>>> the DTB bits but booting a stable kernel without this patch series -
>>>> wouldn't that regress dpaa then for our customers?
>>> These are fixes for issues that popped out after enabling SMMU.
>>> I do not expect them to break anything.
>> That was not my question! You're missing my point: All your patches are
>> lacking a Fixes header in their commit message, for backporting them, to
>> avoid _your DT patches_ breaking the driver on stable branches!
> It does appear that I'm missing your point. For sure, the DT updates solely will
> break the kernel without these fixes but I'm not sure I understand how this
> could happen.
In short, customers rarely run master branch. Kindly have your
colleagues explain stable branches to you in details.
With Fixes header I was referring to the syntax explained here:
> My plan was to share the kernel dts patches sometime after this series
> makes it through.
That's fine. What I'm warning you is that seemingly your DT patches,
once in one of your LSDK U-Boot releases, will cause a regression for
distros like our SLES 15 SP1 unless these prereq kernel patches get
applied on the respective stable branches. Which will not happen
automatically unless you as patch author take the appropriate action
before they get merged.
SUSE Linux GmbH, Maxfeldstr. 5, 90409 NÃrnberg, Germany
GF: Felix ImendÃrffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG NÃrnberg)