From: Greg Malysa <malysagreg@gmail.com>
To: u-boot@lists.denx.de
Cc: philip.molloy@analog.com, adsp-linux@analog.com,
Greg Malysa <malysagreg@gmail.com>,
Arturs Artamonovs <arturs.artamonovs@analog.com>,
Ian Roberts <ian.roberts@timesys.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Joe Hershberger <joe.hershberger@ni.com>,
Nathan Barrett-Morrison <nathan.morrison@timesys.com>,
Peng Fan <peng.fan@nxp.com>, Ramon Fried <rfried.dev@gmail.com>,
Tom Rini <trini@konsulko.com>,
Utsav Agarwal <utsav.agarwal@analog.com>,
Vasileios Bimpikas <vasileios.bimpikas@analog.com>
Subject: [PATCH 0/2] Fix ADI driver header dependencies
Date: Wed, 3 Sep 2025 19:42:00 -0400 [thread overview]
Message-ID: <20250903234205.26787-1-malysagreg@gmail.com> (raw)
Between 2025.07 and 2025.10 many header dependency chains were improved,
but this exposed implicit header usage in several of our drivers. This
wasn't discovered before or included in the original fixes because our
drivers are not yet used by any mainline-supported boards, so build
tests did not find them. This series addresses the two build failures
I've encountered while rebasing our work onto 2025.10 and continuing to
prepare the next submission of our board files.
Greg Malysa (2):
net: dwc_eth_qos_adi: Add missing header
mmc: adi_sdhci: Update headers
drivers/mmc/adi_sdhci.c | 1 +
drivers/net/dwc_eth_qos_adi.c | 1 +
2 files changed, 2 insertions(+)
--
2.45.2
base-commit: 76b8edbc732e327d1e56f08c641f51fdefdbff06
branch: dev/uboot2025.10-fixes
next reply other threads:[~2025-09-03 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 23:42 Greg Malysa [this message]
2025-09-03 23:42 ` [PATCH 1/2] net: dwc_eth_qos_adi: Add missing header Greg Malysa
2025-09-03 23:42 ` [PATCH 2/2] mmc: adi_sdhci: Update headers Greg Malysa
2025-09-04 1:57 ` Peng Fan
2025-09-16 22:06 ` [PATCH 0/2] Fix ADI driver header dependencies 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=20250903234205.26787-1-malysagreg@gmail.com \
--to=malysagreg@gmail.com \
--cc=adsp-linux@analog.com \
--cc=arturs.artamonovs@analog.com \
--cc=ian.roberts@timesys.com \
--cc=jh80.chung@samsung.com \
--cc=joe.hershberger@ni.com \
--cc=nathan.morrison@timesys.com \
--cc=peng.fan@nxp.com \
--cc=philip.molloy@analog.com \
--cc=rfried.dev@gmail.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=utsav.agarwal@analog.com \
--cc=vasileios.bimpikas@analog.com \
/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.