From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Rudi Horn <dyn-git@rudi-horn.de>
Cc: u-boot@lists.denx.de, Andre Przywara <andre.przywara@arm.com>,
Jagan Teki <jagan@amarulasolutions.com>,
linux-sunxi <linux-sunxi@lists.linux.dev>
Subject: Re: [PATCH] Fix detection of odd memory configurations on sunxi
Date: Mon, 08 Sep 2025 16:11:41 +0200 [thread overview]
Message-ID: <2234613.irdbgypaU6@jernej-laptop> (raw)
In-Reply-To: <9c947490-a571-4b35-b3a9-66c8174a7490@rudi-horn.de>
Dne sobota, 16. avgust 2025 ob 14:18:44 Srednjeevropski poletni čas je Rudi Horn napisal(a):
> Hi Jernej,
>
> thanks for the comments on the patch.
>
> > I don't see a benefit for public function here, since it's unlikely
> to be > used anywhere else. Just mark it static. Compiler can optimize
> it better.
>
> My motivation for this was that the implementation relies on subtracting
> `sizeof(u32)` from the address. This is an implementation detail that relies
> on the internals of `mctl_mem_matches_base`, and so I wanted to place
> it in the same file as `mctl_mem_matches_base`, preventing it from being
> static. It will only be called twice, so I don't think optimization is
> too much
> of an issue. However I don't feel strongly on this if you would still prefer
> it in the same file.
>
> Once this is resolved, I will submit another patch with all of the other
> comments addressed.
Ah, right. You can leave as it is.
Best regards,
Jernej
>
> Thanks,
> Rudi
>
>
next prev parent reply other threads:[~2025-09-08 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56f44755-fca8-4364-905e-685e79fd1aea@rudi-horn.de>
2025-08-11 15:25 ` [PATCH] Fix detection of odd memory configurations on sunxi Jernej Škrabec
2025-08-16 12:18 ` Rudi Horn
2025-09-08 14:11 ` Jernej Škrabec [this message]
2025-10-05 0:40 ` Andre Przywara
2025-10-05 6:10 ` Jernej Škrabec
2025-10-05 6:38 ` Jernej Škrabec
2025-10-05 16:30 ` Andre Przywara
2025-10-05 16:16 ` Andre Przywara
2025-10-06 23:09 ` Andre Przywara
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=2234613.irdbgypaU6@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=andre.przywara@arm.com \
--cc=dyn-git@rudi-horn.de \
--cc=jagan@amarulasolutions.com \
--cc=linux-sunxi@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox