From: "Stefan Dösinger" <stefandoesinger@gmail.com>
To: soc@kernel.org
Subject: [GIT PULL] ARM: zte: clean up zx297520v3 doc. warnings
Date: Sat, 23 May 2026 16:11:35 +0300 [thread overview]
Message-ID: <1991560.tdWV9SEqCh@strix> (raw)
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
Hello Arnd,
I am forwarding a patch from Randy Dunlap fixing mistakes I made in my zx29 documentation. I think this should be the last of the zx29 patches for 7.2.
The pull request is based on the current head of your soc/arm branch.
Best regards,
Stefan
The following changes since commit b4e49a4a38fd737f927defb2e9a6562f9ee62f0a:
Merge tag 'zx29-plat-for-7.2' of https://gitlab.com/stefandoesinger/zx297520-kernel into soc/arm (2026-05-20 22:05:46 +0200)
are available in the Git repository at:
https://gitlab.com/stefandoesinger/zx297520-kernel.git tags/zx29-docfix-for-7.2
for you to fetch changes up to 05836235e5412310057ea14e41e24dbc45a429bd:
ARM: zte: clean up zx297520v3 doc. warnings (2026-05-23 15:38:59 +0300)
----------------------------------------------------------------
ARM: zte: clean up zx297520v3 doc. warnings
This pull request contains fixes for building the zx29 SoC documentation
contributed by Randy Dunlap.
----------------------------------------------------------------
Randy Dunlap (1):
ARM: zte: clean up zx297520v3 doc. warnings
Documentation/arch/arm/zte/zx297520v3.rst | 119 +++++++++++++++++++++++++++++++++++++++----------------------------------------
1 file changed, 59 insertions(+), 60 deletions(-)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 870 bytes --]
next reply other threads:[~2026-05-23 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 13:11 Stefan Dösinger [this message]
2026-06-01 20:40 ` [GIT PULL] ARM: zte: clean up zx297520v3 doc. warnings patchwork-bot+linux-soc
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=1991560.tdWV9SEqCh@strix \
--to=stefandoesinger@gmail.com \
--cc=soc@kernel.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