All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio Estevam <festevam@gmail.com>
To: Tom Rini <trini@konsulko.com>
Cc: u-boot@lists.denx.de, "Marek Vasut" <marex@denx.de>,
	"Patrick Delaunay" <patrick.delaunay@foss.st.com>,
	"Pali Rohár" <pali@kernel.org>, "Peng Fan" <peng.fan@nxp.com>
Subject: Re: [PATCH] Revert "common/memsize.c: Fix get_effective_memsize() to check for overflow"
Date: Fri, 6 Jan 2023 17:29:45 -0300	[thread overview]
Message-ID: <CAOMZO5ARUbRvoDykpDTqZkqucuvgpUEoX_KkSmwdZs1BgdS1aQ@mail.gmail.com> (raw)
In-Reply-To: <20230106155143.4025812-1-trini@konsulko.com>

On Fri, Jan 6, 2023 at 12:51 PM Tom Rini <trini@konsulko.com> wrote:
>
> This reverts commit 777aaaa706bcfe08c284aed06886db7d482af3f8.
>
> The changes to this generic function, which is intended to help with
> 32bit platforms with large amounts of memory has unintended side effects
> (which in turn lead to boot failures) on other platforms which were
> previously functional.
>
> Reported-by: Marek Vasut <marex@denx.de>
> Cc: Patrick Delaunay <patrick.delaunay@foss.st.com>
> Cc: Pali Rohár <pali@kernel.org>
> Signed-off-by: Tom Rini <trini@konsulko.com>

Peng also reported an imx issue caused by 777aaaa706bc
(""common/memsize.c: Fix get_effective_memsize() to check for
overflow""):

https://patchwork.ozlabs.org/project/uboot/patch/20221107080016.1304-2-peng.fan@oss.nxp.com/

      parent reply	other threads:[~2023-01-06 20:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 15:51 [PATCH] Revert "common/memsize.c: Fix get_effective_memsize() to check for overflow" Tom Rini
2023-01-06 16:45 ` Pali Rohár
2023-01-06 17:25   ` Tom Rini
2023-01-06 20:22     ` Pali Rohár
2023-01-06 21:14       ` Tom Rini
2023-01-06 21:45         ` Tom Rini
2023-01-06 22:09           ` Pali Rohár
2023-01-06 22:51             ` Tom Rini
2023-01-07 16:26               ` Pali Rohár
2023-01-07 17:32                 ` Tom Rini
2023-01-07 17:38                   ` Pali Rohár
2023-01-07 17:40                     ` Tom Rini
2023-01-07 17:44                       ` Pali Rohár
2023-01-07 17:46                         ` Tom Rini
2023-01-07 21:58                           ` Pali Rohár
2023-01-06 20:29 ` Fabio Estevam [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=CAOMZO5ARUbRvoDykpDTqZkqucuvgpUEoX_KkSmwdZs1BgdS1aQ@mail.gmail.com \
    --to=festevam@gmail.com \
    --cc=marex@denx.de \
    --cc=pali@kernel.org \
    --cc=patrick.delaunay@foss.st.com \
    --cc=peng.fan@nxp.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.