Thread (7 messages) flat view 7 messages, 4 authors, 2015-08-14

Re: [PATCH v2] ARM: shmobile: kzm9g dts: Use adxl345-specific compatible property

From: Simon Horman <horms@verge.net.au>
Date: 2015-07-08 00:51:49
Also in: linux-arm-kernel, linux-devicetree, linux-sh

On Tue, Jul 07, 2015 at 09:56:29AM +0300, Laurent Pinchart wrote:
Hi Simon,

On Tuesday 07 July 2015 09:26:21 Simon Horman wrote:
quoted
On Mon, Jul 06, 2015 at 04:29:33PM +0300, Laurent Pinchart wrote:
quoted
On Monday 06 July 2015 12:55:32 Geert Uytterhoeven wrote:
quoted
Replace the deprecated generic "adi,adxl34x" compatible value by the
adxl345-specific "adi,adxl345" value, cfr. commit e465bf6fc55d5ce2 ("DT:
i2c: Deprecate adi,adxl34x compatible string").

Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Acked-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
quoted
---
Depends on commit 3a38958d2477b718 ("Input: adxl34x - add OF match
support"), which is in v4.2-rc1.

This is v2 of "ARM: shmobile: kzm9g dts: Add adxl345-specific compatible
property".
It appears to me that this will cause a regression when booting old kernels
with new dts blobs. For that reason think we should consider v1
of this change coupled with a schedule to remove use of the deprecated
compat string.
That's the forward compatibility that Geert mentioned, is that really an 
issue, especially on this board ?
I think it would be best to provide backwards compatibility unless there
is a compelling reason not to.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help