From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Rob Herring <robh@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org,
Ralf Baechle <ralf@linux-mips.org>,
Paul Burton <paulburton@kernel.org>
Subject: Re: [PATCH v1] MIPS: Malta: fix alignment of the devicetree buffer
Date: Thu, 2 Sep 2021 11:03:24 +0200 [thread overview]
Message-ID: <20210902090324.GA6429@alpha.franken.de> (raw)
In-Reply-To: <20210902071951.28722-1-o.rempel@pengutronix.de>
On Thu, Sep 02, 2021 at 09:19:51AM +0200, Oleksij Rempel wrote:
> Starting with following patch MIPS Malta is not able to boot:
> | commit 79edff12060fe7772af08607eff50c0e2486c5ba
> | Author: Rob Herring <robh@kernel.org>
> | scripts/dtc: Update to upstream version v1.6.0-51-g183df9e9c2b9
>
> The reason is the alignment test added to the fdt_ro_probe_(). To fix
> this issue, we need to make sure that fdt_buf is aligned.
>
> Since the dtc patch was designed to uncover potential issue, I handle
> initial MIPS Malta patch as initial bug.
>
> Fixes: e81a8c7dabac ("MIPS: Malta: Setup RAM regions via DT")
> Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> ---
> arch/mips/mti-malta/malta-dtshim.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2021-09-02 9:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 7:19 [PATCH v1] MIPS: Malta: fix alignment of the devicetree buffer Oleksij Rempel
2021-09-02 9:03 ` Thomas Bogendoerfer [this message]
2021-09-02 10:14 ` Marc Kleine-Budde
2021-10-10 9:58 ` Maciej W. Rozycki
2021-10-11 7:15 ` Oleksij Rempel
2021-10-11 8:09 ` Maciej W. Rozycki
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=20210902090324.GA6429@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=paulburton@kernel.org \
--cc=ralf@linux-mips.org \
--cc=robh@kernel.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).