From: Bjorn Andersson <andersson@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
"Andrew Davis" <afd@ti.com>,
"Barnabás Czémán" <barnabas.czeman@mainlining.org>,
"Claudiu Beznea" <claudiu.beznea.uj@bp.renesas.com>,
"Thorsten Blum" <thorsten.blum@linux.dev>
Subject: [GIT PULL] rpmsg updates for v6.18
Date: Thu, 2 Oct 2025 09:05:21 -0500 [thread overview]
Message-ID: <20251002140524.64158-1-andersson@kernel.org> (raw)
The following changes since commit c17b750b3ad9f45f2b6f7e6f7f4679844244f0b9:
Linux 6.17-rc2 (2025-08-17 15:22:10 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git tags/rpmsg-v6.18
for you to fetch changes up to 09390ed9af37ed612dd0967ff2b0d639872b8776:
rpmsg: qcom_smd: Fix fallback to qcom,ipc parse (2025-09-20 21:29:48 -0500)
----------------------------------------------------------------
rpmsg updates for v6.18
Clean up the dev_pm_domain integration in rpmsg core. Correct module
aliases for the rpmsg char driver.
Transition Qualcomm SMD and GLINK drivers to strscpy() and fix the
regression in legacy code for acquiring outgoing interrupts using the
non-mailbox based mechanism.
----------------------------------------------------------------
Andrew Davis (1):
rpmsg: char: Export alias for RPMSG ID rpmsg-raw from table
Barnabás Czémán (1):
rpmsg: qcom_smd: Fix fallback to qcom,ipc parse
Claudiu Beznea (1):
rpmsg: core: Drop dev_pm_domain_detach() call
Thorsten Blum (1):
rpmsg: Use strscpy() instead of strscpy_pad()
drivers/rpmsg/qcom_glink_native.c | 2 +-
drivers/rpmsg/qcom_smd.c | 4 ++--
drivers/rpmsg/rpmsg_char.c | 3 ++-
drivers/rpmsg/rpmsg_core.c | 5 ++---
4 files changed, 7 insertions(+), 7 deletions(-)
next reply other threads:[~2025-10-02 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 14:05 Bjorn Andersson [this message]
2025-10-04 23:42 ` [GIT PULL] rpmsg updates for v6.18 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=20251002140524.64158-1-andersson@kernel.org \
--to=andersson@kernel.org \
--cc=afd@ti.com \
--cc=barnabas.czeman@mainlining.org \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=thorsten.blum@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