linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 15 Jan 2018 09:52:31 +0530	[thread overview]
Message-ID: <20180115042231.GA22978@vireshk-i7> (raw)
In-Reply-To: <CAK8P3a3MZX-ZsxX9h1-8kVQhn9hqY=c8L1+=e3uTfjEjBCYuPg@mail.gmail.com>

On 12-01-18, 23:05, Arnd Bergmann wrote:
> I've sent patches for all the remaining MODULE_LICENSE warnings earlier
> this week, and we should now have patches for almost all the dtc
> warnings in flight. This is what I still see on my randconfig builder
> with linux-next + arm-soc/for-next + patches I sent:
> 
>      arch/arm/boot/dts/spear1310-evb.dtb: Warning (gpios_property):
> Missing property '#gpio-cells' in node /interrupt-controller at ec801000
> or bad phandle (referred from /ahb/apb/spi at e0100000:cs-gpios[6])
>      arch/arm/boot/dts/spear1310-evb.dtb: Warning (gpios_property):
> Property 'cs-gpios', cell 6 is not a phandle reference in
> /ahb/apb/spi at e0100000
>      arch/arm/boot/dts/spear1340-evb.dtb: Warning (dmas_property):
> Missing property '#dma-cells' in node /interrupt-controller at ec801000
> or bad phandle (referred from /ahb/apb/serial at b4100000:dmas[4])
>      arch/arm/boot/dts/spear1340-evb.dtb: Warning (dmas_property):
> Property 'dmas', cell 4 is not a phandle reference in
> /ahb/apb/serial at b4100000
>      arch/arm/boot/dts/spear600-evb.dtb: Warning
> (interrupts_property): Missing interrupt-parent for
> /ahb/apb/rtc at fc900000

These are all the warnings we got earlier. So none of my patches are in the
branch you tested I believe. Can you do a `git log` and see if they are present
?

-- 
viresh

  parent reply	other threads:[~2018-01-15  4: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
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 [this message]
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=20180115042231.GA22978@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;
as well as URLs for NNTP newsgroup(s).