From: Yao Zi <me@ziyao.cc>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH RESEND 14/14] treewide: Clean up DECLARE_GLOBAL_DATA_PTR usage
Date: Thu, 5 Feb 2026 08:46:00 +0000 [thread overview]
Message-ID: <aYRX6nyav7tZ5prW@pie> (raw)
In-Reply-To: <20260203114702.1867224-2-peng.fan@oss.nxp.com>
On Tue, Feb 03, 2026 at 07:47:01PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> Remove DECLARE_GLOBAL_DATA_PTR from files where gd is not used, and
> drop the unnecessary inclusion of asm/global_data.h.
>
> Headers should be included directly by the files that need them,
> rather than indirectly via global_data.h.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
For TH1520 changes,
Acked-by: Yao Zi <me@ziyao.cc>
Thanks for the clean up!
Regards,
Yao Zi
prev parent reply other threads:[~2026-02-05 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 11:47 [PATCH RESEND 13/14] socfpga: clock_manager_s10: Add missing header files Peng Fan (OSS)
2026-02-03 11:47 ` [PATCH RESEND 14/14] treewide: Clean up DECLARE_GLOBAL_DATA_PTR usage Peng Fan (OSS)
2026-02-03 12:44 ` Patrice CHOTARD
2026-02-04 4:52 ` Anshul Dalal
2026-02-05 8:46 ` Yao Zi [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=aYRX6nyav7tZ5prW@pie \
--to=me@ziyao.cc \
--cc=peng.fan@oss.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox