From: Angelo Dureghello <angelo@kernel-space.org>
To: Rasmus Villemoes <ravi@prevas.dk>
Cc: u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>,
Alexey Brodkin <alexey.brodkin@synopsys.com>,
"NXP i.MX U-Boot Team" <uboot-imx@nxp.com>,
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 06/12] m68k: drop pointless #if 0 block
Date: Thu, 5 Jun 2025 10:45:02 +0200 [thread overview]
Message-ID: <20250605104502.54e16e7a@archlinux> (raw)
In-Reply-To: <20250604195612.2312979-7-ravi@prevas.dk>
thanks,
Acked-by: Angelo Dureghello <angelo@kernel-space.org>
On Wed, 4 Jun 2025 21:56:06 +0200
Rasmus Villemoes <ravi@prevas.dk> wrote:
> The way DECLARE_GLOBAL_DATA_PTR is used, the stuff under #if 0 can
> never compile as you cannot have a non-constant initializer at global
> scope (and one would get linker errors as well because the 'gd' symbol
> would be defined in multiple TUs).
>
> Signed-off-by: Rasmus Villemoes <ravi@prevas.dk>
> ---
> arch/m68k/include/asm/global_data.h | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/arch/m68k/include/asm/global_data.h b/arch/m68k/include/asm/global_data.h
> index 29b46645676..aea2ccabe08 100644
> --- a/arch/m68k/include/asm/global_data.h
> +++ b/arch/m68k/include/asm/global_data.h
> @@ -32,11 +32,6 @@ struct arch_global_data {
>
> #include <asm-generic/global_data.h>
>
> -#if 0
> -extern gd_t *global_data;
> -#define DECLARE_GLOBAL_DATA_PTR gd_t *gd = global_data
> -#else
> #define DECLARE_GLOBAL_DATA_PTR register gd_t *gd asm ("d7")
> -#endif
>
> #endif /* __ASM_GBL_DATA_H */
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-06-05 8:46 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 [this message]
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 ` [PATCH 00/12] drop volatile from global data Tom Rini
2025-06-04 20:40 ` 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=20250605104502.54e16e7a@archlinux \
--to=angelo@kernel-space.org \
--cc=alexey.brodkin@synopsys.com \
--cc=daniel.schwierzeck@gmail.com \
--cc=michal.simek@amd.com \
--cc=ravi@prevas.dk \
--cc=rick@andestech.com \
--cc=trini@konsulko.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.