linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: dtc warnings
Date: Fri, 1 Apr 2016 08:42:37 -0700	[thread overview]
Message-ID: <20160401154237.GK9329@atomide.com> (raw)
In-Reply-To: <CAL_Jsq+=OjY8y_8x7OSm-MWYKbrHN5cbv4TLwULxhNq+gfiMtw@mail.gmail.com>

Hi,

* Rob Herring <robh@kernel.org> [160331 18:42]:
> You may have noticed that linux-next had gotten noisy with dtc
> warnings lately. I dropped the change for a bit, but added it back
> today except now it is disabled unless building with "W=1".
> 
> There's ~25K (2500 unique) warnings generated from the ARM dts files.
> Here's the ranking of warnings by dtb. OMAP is the clear winner (based
> on the similar counts, probably lots of duplicates). Please help
> remind contributors to test with W=1 and start to fix these.

I think Tero already has been looking at fixing the omap clock
related warnings that seem to produce most of these, so adding
him to Cc.

Regards,

Tony

  parent reply	other threads:[~2016-04-01 15:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-01  1:40 dtc warnings Rob Herring
2016-04-01  7:49 ` Tomi Valkeinen
2016-04-01  7:53   ` Krzysztof Kozlowski
2016-04-01 13:57     ` Nishanth Menon
2016-04-03  6:59       ` Viresh Kumar
2016-04-03  8:08         ` Krzysztof Kozlowski
2016-04-03 12:27           ` Viresh Kumar
2016-04-04  5:16             ` Rob Herring
2016-04-04  5:50               ` Viresh Kumar
2016-04-04  5:56                 ` Krzysztof Kozlowski
2016-04-01 13:25   ` Rob Herring
2016-04-01 15:42 ` Tony Lindgren [this message]
2016-04-21 12:47 ` Rob Herring

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=20160401154237.GK9329@atomide.com \
    --to=tony@atomide.com \
    --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).