From: viresh.kumar@linaro.org (Viresh Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] arm: spear600: Add missing interrupt-parent of rtc
Date: Fri, 12 Jan 2018 08:52:23 +0530 [thread overview]
Message-ID: <20180112032223.GK3626@vireshk-i7> (raw)
In-Reply-To: <20180112020711.6gp2pnsxxjzelidq@localhost>
On 11-01-18, 18:07, Olof Johansson 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 at vger.kernel.org # v3.8+
> > Reported-by: Arnd Bergmann <arnd@arndb.de>
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
>
> Applied to next/dt. Is stable really needed on this? It's been broken since
> pretty much forever, and nobody has complained... :)
Not sure. Just thought it may be useful for someone somewhere :)
--
viresh
next prev parent reply other threads:[~2018-01-12 3:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 5:58 [PATCH 1/3] arm: spear600: Add missing interrupt-parent of rtc Viresh Kumar
2018-01-11 5:58 ` [PATCH 2/3] arm: spear13xx: Fix dmas cells Viresh Kumar
2018-01-12 2:07 ` Olof Johansson
2018-01-11 5:58 ` [PATCH 3/3] arm: spear13xx: Fix spics gpio controller's warning Viresh Kumar
2018-01-12 2:07 ` Olof Johansson
2018-01-11 13:47 ` [PATCH 1/3] arm: spear600: Add missing interrupt-parent of rtc Rob Herring
2018-01-12 2:07 ` Olof Johansson
2018-01-12 3:22 ` Viresh Kumar [this message]
2018-01-12 3:23 ` Olof Johansson
2018-01-12 8:56 ` Arnd Bergmann
2018-01-12 18:23 ` Olof Johansson
2018-01-12 20:45 ` Rob Herring
2018-01-12 21:50 ` Olof Johansson
2018-01-12 21:53 ` Arnd Bergmann
2018-01-12 21:57 ` Olof Johansson
2018-01-12 22:05 ` Arnd Bergmann
2018-01-14 11:20 ` Linus Walleij
2018-01-15 16:34 ` Arnd Bergmann
2018-01-15 4:22 ` Viresh Kumar
2018-01-15 12:49 ` Arnd Bergmann
2018-01-14 11:17 ` Linus Walleij
2018-01-14 13:17 ` Alexandre Belloni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180112032223.GK3626@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox