[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171017204959.kfbhn2yxhv2sb5qg@rob-hp-laptop>
Date: Tue, 17 Oct 2017 15:50:00 -0500
From: Rob Herring <robh@...nel.org>
To: Jerome Brunet <jbrunet@...libre.com>
Cc: Kevin Hilman <khilman@...libre.com>,
Carlo Caione <carlo@...one.org>, devicetree@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-amlogic@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] firmware: meson-sm: use generic compatible
On Thu, Oct 12, 2017 at 03:47:43PM +0200, Jerome Brunet wrote:
> The meson secure monitor seems to be compatible with more SoCs than
> initially thought. Let's use the most generic compatible he have in
> DT instead of the gxbb specific one
>
> Signed-off-by: Jerome Brunet <jbrunet@...libre.com>
> ---
> Documentation/devicetree/bindings/firmware/meson/meson_sm.txt | 4 ++--
> drivers/firmware/meson/meson_sm.c | 4 ++--
> 2 files changed, 4 insertions(+), 4 deletions(-)
Seems like a pointless, not backwards compatible change to me. In the
end, it's just a string to match on. Who cares what the string is.
Rob
Powered by blists - more mailing lists