mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ohad Ben-Cohen <ohad@wizery.com>,
	linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Arun Kumar Neelakantam <aneela@codeaurora.org>,
	Alexandru Ardelean <ardeleanalex@gmail.com>,
	Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>,
	Cai Huoqing <caihuoqing@baidu.com>,
	Chris Lew <clew@codeaurora.org>,
	Kees Cook <keescook@chromium.org>,
	Tinghan Shen <tinghan.shen@mediatek.com>
Subject: [GIT PULL] rpmsg updates for v5.16
Date: Mon,  8 Nov 2021 11:23:57 -0600	[thread overview]
Message-ID: <20211108172357.2477129-1-bjorn.andersson@linaro.org> (raw)

The following changes since commit 6880fa6c56601bb8ed59df6c30fd390cc5f6dd8f:

  Linux 5.15-rc1 (2021-09-12 16:28:37 -0700)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/remoteproc/linux.git tags/rpmsg-v5.16

for you to fetch changes up to b16a37e1846c9573a847a56fa2f31ba833dae45a:

  rpmsg: glink: Send READ_NOTIFY command in FIFO full case (2021-10-15 11:02:11 -0500)

----------------------------------------------------------------
rpmsg updates for v5.16

For the GLINK implementation this adds support for splitting outgoing
messages that are too large to fit in the fifo, it introduces the use of
"read notifications", to avoid polling in the case where the outgoing
fifo is full and a few bugs are squashed.

The return value of rpmsg_create_ept() for when RPMSG is disabled is
corrected to return a valid error, the Mediatek rpmsg driver is updated
to match the DT binding and a couple of cleanups are done in the virtio
rpmsg driver.

----------------------------------------------------------------
Alexandru Ardelean (1):
      rpmsg: virtio_rpmsg_bus: use dev_warn_ratelimited for msg with no recipient

Arnaud Pouliquen (1):
      rpmsg: Fix rpmsg_create_ept return when RPMSG config is not defined

Arun Kumar Neelakantam (3):
      rpmsg: glink: Add TX_DATA_CONT command while sending
      rpmsg: glink: Remove the rpmsg dev in close_ack
      rpmsg: glink: Send READ_NOTIFY command in FIFO full case

Cai Huoqing (1):
      rpmsg: virtio: Remove unused including <linux/of_device.h>

Chris Lew (1):
      rpmsg: glink: Remove channel decouple from rpdev release

Kees Cook (1):
      rpmsg: glink: Replace strncpy() with strscpy_pad()

Tinghan Shen (1):
      rpmsg: Change naming of mediatek rpmsg property

 drivers/rpmsg/mtk_rpmsg.c         |  2 +-
 drivers/rpmsg/qcom_glink_native.c | 90 +++++++++++++++++++++++++++++++++++----
 drivers/rpmsg/virtio_rpmsg_bus.c  |  3 +-
 include/linux/rpmsg.h             |  2 +-
 4 files changed, 85 insertions(+), 12 deletions(-)

             reply	other threads:[~2021-11-08 17:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08 17:23 Bjorn Andersson [this message]
2021-11-10 17:44 ` 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=20211108172357.2477129-1-bjorn.andersson@linaro.org \
    --to=bjorn.andersson@linaro.org \
    --cc=aneela@codeaurora.org \
    --cc=ardeleanalex@gmail.com \
    --cc=arnaud.pouliquen@foss.st.com \
    --cc=caihuoqing@baidu.com \
    --cc=clew@codeaurora.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=ohad@wizery.com \
    --cc=tinghan.shen@mediatek.com \
    --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®