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: Two new breakages since Thursday
Date: Tue, 14 Apr 2015 08:05:00 -0700	[thread overview]
Message-ID: <20150414150459.GD18048@atomide.com> (raw)
In-Reply-To: <4781251.nAZ9xiIQGV@wuerfel>

* Arnd Bergmann <arnd@arndb.de> [150414 08:00]:
> On Tuesday 14 April 2015 07:28:47 Tony Lindgren wrote:
> > > I managed to catch up with my email last night and pulled in these two fixes
> > > as well as a number of others that we had neglected over the last two weeks.
> > > 
> > > I found one new regression with the overnight build tests in a branch I pulled
> > > in as 'next/late' from Tony, and backed that out now. I'll wait for you and
> > > Stephen Rothwell (who also reported these issues) to confirm that it's ok
> > > now and we'll hopefully be ready to send pull requests by the end of the
> > > week.
> > 
> > Hmm what's this issue you're mentioning here for the next/late? Is it the
> > merge conflict with camera related changes fixed up by Stephen Rothwell
> > in next?
> > 
> > 
> 
> This is the error I get during 'make dtbs':
> 
>   DTC     arch/arm/boot/dts/am3517_mt_ventoux.dtb
> ERROR (phandle_references): Reference to non-existent node or label "omap3_scm_general"
> 
> The problem is evidently commit b8845074cfbbd ("ARM: dts: omap3: add
> minimal l4 bus layout with control module support"), which for some reason
> removes the tisyscon at 48002270 node that is still referenced through
> the &omap3_scm_general label from omap34xx.dtsi and omap36xx.dtsi.

I believe this issue got introduced on the 7th by the camera patches
I acked earlier. Stephen has been carrying this fix in next:

https://lkml.org/lkml/2015/4/6/436

The problem was we had two different SCM dts entries.. So with Tero's
changes we've now standardized on scm_conf.

Reagrds,

Tony

  reply	other threads:[~2015-04-14 15:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-05  8:06 Two new breakages since Thursday Russell King - ARM Linux
2015-04-05 10:12 ` Alexandre Belloni
2015-04-05 19:50   ` Nicolas Ferre
2015-04-11  9:00 ` Russell King - ARM Linux
2015-04-13 16:18   ` Yingjoe Chen
2015-04-13 22:41     ` Arnd Bergmann
2015-04-14  9:26       ` Russell King - ARM Linux
2015-04-14  9:34         ` Arnd Bergmann
2015-04-14 14:28           ` Tony Lindgren
2015-04-14 14:59             ` Arnd Bergmann
2015-04-14 15:05               ` Tony Lindgren [this message]
2015-04-14 16:21                 ` Tony Lindgren
2015-04-15 19:50                   ` Arnd Bergmann
2015-04-15 20:00                     ` Tony Lindgren

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=20150414150459.GD18048@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).