From: "Arnd Bergmann" <arnd@arndb.de>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: soc@lists.linux.dev, linux-kernel@vger.kernel.org,
"Krzysztof Kozlowski" <krzk@kernel.org>
Subject: [GIT PULL] soc: build fix for 6.18
Date: Fri, 03 Oct 2025 00:43:59 +0200 [thread overview]
Message-ID: <417683c6-434e-4ae3-b361-cdf25e01d943@app.fastmail.com> (raw)
The following changes since commit 8f5ae30d69d7543eee0d70083daf4de8fe15d585:
Linux 6.17-rc1 (2025-08-10 19:41:16 +0300)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/soc/soc.git tags/soc-fixes-6.18
for you to fetch changes up to 91f98de42310c70f9a23595b3b20aa305717d955:
dt-bindings: clock: Add ARTPEC-8 clock controller (2025-08-31 15:22:10 +0200)
----------------------------------------------------------------
soc: build fix for 6.18
One commit for the dt bindings was missing from the dt branch, this
one is already pending in the clk tree that contains the corresponding
device driver.
----------------------------------------------------------------
Linus, please either take this one if the build breakage keeps
bothering you, or wait for the common-clk tree pull request that
contains the same 91f98de42310 commit.
Sorry for missing the obvious build failure.
Hakyeong Kim (1):
dt-bindings: clock: Add ARTPEC-8 clock controller
.../bindings/clock/axis,artpec8-clock.yaml | 213 +++++++++++++++++++++
include/dt-bindings/clock/axis,artpec8-clk.h | 169 ++++++++++++++++
2 files changed, 382 insertions(+)
create mode 100644 Documentation/devicetree/bindings/clock/axis,artpec8-clock.yaml
create mode 100644 include/dt-bindings/clock/axis,artpec8-clk.h
next reply other threads:[~2025-10-02 22:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 22:43 Arnd Bergmann [this message]
2025-10-04 2:41 ` pr-tracker-bot
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=417683c6-434e-4ae3-b361-cdf25e01d943@app.fastmail.com \
--to=arnd@arndb.de \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®