[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d086216f-f3fc-c88a-3891-81e84e8bdb01@suse.de>
Date: Fri, 31 May 2019 18:15:22 +0200
From: Andreas Färber <afaerber@...e.de>
To: laurentiu.tudor@....com
Cc: netdev@...r.kernel.org, madalin.bucur@....com, roy.pledge@....com,
camelia.groza@....com, leoyang.li@....com,
linux-kernel@...r.kernel.org, Joakim.Tjernlund@...inera.com,
iommu@...ts.linux-foundation.org, linuxppc-dev@...ts.ozlabs.org,
davem@...emloft.net, linux-arm-kernel@...ts.infradead.org,
Mian Yousaf Kaukab <yousaf.kaukab@...e.com>
Subject: Re: [PATCH v3 0/6] Prerequisites for NXP LS104xA SMMU enablement
Hi Laurentiu,
Am 30.05.19 um 16:19 schrieb laurentiu.tudor@....com:
> 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?
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah
HRB 21284 (AG Nürnberg)
Powered by blists - more mailing lists