From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] mvebu: Fix fixup of mbus device-tree ranges
Date: Sat, 25 Feb 2017 21:41:14 +0100 [thread overview]
Message-ID: <20170225204114.dzrcbu2my6zhiqjj@pengutronix.de> (raw)
In-Reply-To: <20170224071225.xqzj5v75fgbnxweo@pengutronix.de>
Hallo,
On Fri, Feb 24, 2017 at 08:12:25AM +0100, Sascha Hauer wrote:
> On Wed, Feb 22, 2017 at 09:06:18PM +0100, Uwe Kleine-König wrote:
> > Commits "mvebu: {armada-370-xp,dove,kirkwood}: simplify soc init code
> > flow" simplified too much. The problem is that if the dtb used for
> > probing doesn't use the same mbus window address as barebox (i.e.
> > 0xf1000000) the fixup fails because above commits moved the information
> > about the real position to a postcore initcall which is too late because
> > the fixup happens in of_arm_init which runs as core initcall.
>
> Said patches are currently in -next, so you could send a fixup patch
> instead or I could just remove the patches.
As the commit log isn't correct with this squashed in I sent a v2 and
not a fixup for them.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-02-25 20:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 20:06 Uwe Kleine-König
2017-02-24 7:12 ` Sascha Hauer
2017-02-25 20:41 ` Uwe Kleine-König [this message]
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=20170225204114.dzrcbu2my6zhiqjj@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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