Hi Greg,
This patch should have been picked for the 5.18 branch where the device tree binding was introcuded first, but instead it landed in -next without a Fixes: tag [1].
Now there is a backwards incompatible change between 5.18 and the upcoming 5.19. Thus, can this be picked up for the 5.18 tree?
More background can be found in [2].
-michael
[1] https://lore.kernel.org/r/3b8fc56f64508f7604f3b9e14b048568@walle.cc [2] https://lore.kernel.org/r/4a45db184fbadc278624571dfbeb5004@walle.cc
On Wed, Jun 22, 2022 at 01:48:10PM +0200, Michael Walle wrote:
Hi Greg,
This patch should have been picked for the 5.18 branch where the device tree binding was introcuded first, but instead it landed in -next without a Fixes: tag [1].
Now there is a backwards incompatible change between 5.18 and the upcoming 5.19. Thus, can this be picked up for the 5.18 tree?
More background can be found in [2].
-michael
[1] https://lore.kernel.org/r/3b8fc56f64508f7604f3b9e14b048568@walle.cc [2] https://lore.kernel.org/r/4a45db184fbadc278624571dfbeb5004@walle.cc
Now queued up, thanks.
greg k-h
linux-stable-mirror@lists.linaro.org