All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Krzysztof Kozlowski <krzk@kernel.org>,
	"Ricardo B . Marliere" <ricardo@marliere.net>
Subject: [GIT PULL] rpmsg updates for v6.10
Date: Mon, 20 May 2024 19:58:46 -0700	[thread overview]
Message-ID: <20240521025847.231912-1-andersson@kernel.org> (raw)


The following changes since commit 4cece764965020c22cff7665b18a012006359095:

  Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git tags/rpmsg-v6.10

for you to fetch changes up to bcbab579f968ffd63236d90227212e689ddbd600:

  rpmsg: qcom_glink_ssr: fix module autoloading (2024-05-06 19:26:28 -0700)

----------------------------------------------------------------
rpmsg updates for v6.10

This makes core rpmsg_class const and it ensures automatic module
loading of the Qualcomm glink_ssr driver happens.

----------------------------------------------------------------
Krzysztof Kozlowski (1):
      rpmsg: qcom_glink_ssr: fix module autoloading

Ricardo B. Marliere (1):
      rpmsg: core: Make rpmsg_class constant

 drivers/rpmsg/qcom_glink_ssr.c |  1 +
 drivers/rpmsg/rpmsg_char.c     |  2 +-
 drivers/rpmsg/rpmsg_core.c     | 16 +++++++++-------
 drivers/rpmsg/rpmsg_ctrl.c     |  2 +-
 drivers/rpmsg/rpmsg_internal.h |  2 +-
 5 files changed, 13 insertions(+), 10 deletions(-)

             reply	other threads:[~2024-05-21  2:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-21  2:58 Bjorn Andersson [this message]
2024-05-21 18:13 ` [GIT PULL] rpmsg updates for v6.10 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=20240521025847.231912-1-andersson@kernel.org \
    --to=andersson@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=ricardo@marliere.net \
    --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 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.