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,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Arvind Yadav <arvind.yadav.cs@gmail.com>
Subject: [GIT PULL] rpmsg updates for v4.17
Date: Mon, 9 Apr 2018 15:25:09 -0700 [thread overview]
Message-ID: <20180409222509.GC17344@builder> (raw)
The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2:
Linux 4.16-rc1 (2018-02-11 15:04:29 -0800)
are available in the Git repository at:
git://github.com/andersson/remoteproc tags/rpmsg-v4.17
for you to fetch changes up to 0d72038c303c616a63415a07366f916b5edc3830:
rpmsg: smd: Use announce_create to process any receive work (2018-03-27 21:54:37 -0700)
----------------------------------------------------------------
rpmsg updates for v4.17
This transitions the rpmsg_trysend() code paths of SMD and GLINK to use
non-sleeping locks, it reverts the overly optimistic handling of
discovered SMD channels and fixes an issue in SMD where incoming
messages races with the probing of a client driver.
----------------------------------------------------------------
Arvind Yadav (2):
rpmsg: glink: use put_device() if device_register fail
rpmsg: smd: use put_device() if device_register fail
Bjorn Andersson (6):
rpmsg: smd: Use spinlock in tx path
rpmsg: glink: Use spinlock in tx path
Revert "rpmsg: smd: Create device for all channels"
rpmsg: smd: Fix container_of macros
rpmsg: Only invoke announce_create for rpdev with endpoints
rpmsg: smd: Use announce_create to process any receive work
drivers/rpmsg/qcom_glink_native.c | 18 ++++++++------
drivers/rpmsg/qcom_glink_smem.c | 3 ++-
drivers/rpmsg/qcom_smd.c | 51 +++++++++++++++++++++++++++++----------
drivers/rpmsg/rpmsg_core.c | 2 +-
4 files changed, 52 insertions(+), 22 deletions(-)
reply other threads:[~2018-04-09 22:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180409222509.GC17344@builder \
--to=bjorn.andersson@linaro.org \
--cc=arvind.yadav.cs@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.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 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.