Hi,
On 14/01/2018 at 12:17:23 +0100, Linus Walleij wrote:
> On Fri, Jan 12, 2018 at 3:07 AM, Olof Johansson <olof@xxxxxxxxx> wrote:
> > On Thu, Jan 11, 2018 at 11:28:51AM +0530, Viresh Kumar wrote:
> >> The interrupt-parent of rtc was missing, add it.
> >>
> >> Fixes: 8113ba917dfa ("ARM: SPEAr: DT: Update device nodes")
> >> Cc: stable@xxxxxxxxxxxxxxx # v3.8+
> >> Reported-by: Arnd Bergmann <arnd@xxxxxxxx>
> >> Signed-off-by: Viresh Kumar <viresh.kumar@xxxxxxxxxx>
> >
> > Applied to next/dt. Is stable really needed on this? It's been broken since
> > pretty much forever, and nobody has complained... :)
>
> The SPEAr architecture is widely used (in modified variants) by
> a large industrial automation company, 20+ years of support cycle.
>
> However I think they have a forked both kernel and hardware, so they
> will not notice any time soon, and when they eventually upgrade they
> can simply pick the latest I guess.
>
We have a customer using mainline v4.14 on their Spear600 based
products.
I guess the reason why nobody complained is simply because nobody is
using the SoC RTC ;)
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
