All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: Rasmus Villemoes <ravi@prevas.dk>
Cc: u-boot@lists.denx.de,
	Alexey Brodkin <alexey.brodkin@synopsys.com>,
	"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
	Angelo Dureghello <angelo@kernel-space.org>,
	Michal Simek <michal.simek@amd.com>,
	Daniel Schwierzeck <daniel.schwierzeck@gmail.com>,
	Rick Chen <rick@andestech.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	uboot-snps-arc@synopsys.com
Subject: Re: [PATCH 00/12] drop volatile from global data
Date: Wed, 4 Jun 2025 14:07:02 -0600	[thread overview]
Message-ID: <20250604200702.GS1382132@bill-the-cat> (raw)
In-Reply-To: <20250604195612.2312979-1-ravi@prevas.dk>

[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]

On Wed, Jun 04, 2025 at 09:56:00PM +0200, Rasmus Villemoes wrote:
> There's really no reason for the gd pointer to have the volatile
> qualifier.
> 
> In fact, I claim that it's completely unnecessary and just pessimizes
> code generation and forces ugly casts in lots of places. For example,
> see the casts in drivers/core/tag.c where elements are added to
> gd->dm_taglist, or a helper such as cyclic_get_list() that should not
> be needed.
> 
> Also, it is what ends up standing in the way of an otherwise
> innocent code cleanup of list.h:
> https://lore.kernel.org/u-boot/20250522165656.GB2179216@bill-the-cat/
> 
> Note that riscv, x86 as well as arm64 with LTO enabled has not had
> this volatile qualifier, so it's unlikely there's any generic code
> that depends on it.
> 
> CI seems mostly happy:
> 
>   https://github.com/u-boot/u-boot/pull/775/checks?check_run_id=43463083829
> 
> The one failing test seems to be an infrastructure thing unrelated to
> these patches ("docker: filesystem layer verification failed for
> digest
> sha256:379cc6cd06dc3fc80e31d5170204c0cfcc25cb3b3ad457ced23bed2b38ec9f36")

Azure seems to be having some hiccups, sadly. I know from my end I can't
hit "rerun failed jobs", is there an option visible to you like that?
Thanks.

-- 
Tom

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  parent reply	other threads:[~2025-06-04 20:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04 19:56 [PATCH 00/12] drop volatile from global data Rasmus Villemoes
2025-06-04 19:56 ` [PATCH 01/12] arm: drop volatile qualifier from gd pointer Rasmus Villemoes
2025-06-09  8:01   ` Anshul Dalal
2025-06-04 19:56 ` [PATCH 02/12] powerpc: " Rasmus Villemoes
2025-06-04 19:56 ` [PATCH 03/12] mips: " Rasmus Villemoes
2025-06-04 19:56 ` [PATCH 04/12] microblaze: " Rasmus Villemoes
2025-06-04 19:56 ` [PATCH 05/12] m68k: " Rasmus Villemoes
2025-06-04 19:56 ` [PATCH 06/12] m68k: drop pointless #if 0 block Rasmus Villemoes
2025-06-05  8:45   ` Angelo Dureghello
2025-06-04 19:56 ` [PATCH 07/12] arc: drop volatile qualifier from gd pointer Rasmus Villemoes
2025-06-04 19:56 ` [PATCH 08/12] arm: imx: remove unnecessary volatile qualifiers from "save gd" variables Rasmus Villemoes
2025-06-09  8:01   ` Anshul Dalal
2025-06-04 19:56 ` [PATCH 09/12] efi: drop volatile qualifier " Rasmus Villemoes
2025-06-05  5:09   ` Heinrich Schuchardt
2025-06-04 19:56 ` [PATCH 10/12] lib/trace: " Rasmus Villemoes
2025-06-04 19:56 ` [PATCH 11/12] arm: remove volatile from set_gd prototype Rasmus Villemoes
2025-06-04 19:56 ` [PATCH 12/12] riscv: " Rasmus Villemoes
2025-06-04 20:07 ` Tom Rini [this message]
2025-06-04 20:40   ` [PATCH 00/12] drop volatile from global data Rasmus Villemoes
2025-06-05 14:23     ` Tom Rini
2025-06-04 22:47   ` Tom Rini
2025-06-14 13:56 ` Tom Rini

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=20250604200702.GS1382132@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=alexey.brodkin@synopsys.com \
    --cc=angelo@kernel-space.org \
    --cc=daniel.schwierzeck@gmail.com \
    --cc=michal.simek@amd.com \
    --cc=ravi@prevas.dk \
    --cc=rick@andestech.com \
    --cc=u-boot@lists.denx.de \
    --cc=uboot-imx@nxp.com \
    --cc=uboot-snps-arc@synopsys.com \
    --cc=xypron.glpk@gmx.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.