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>,
Dan Carpenter <dan.carpenter@oracle.com>,
Pravin Shedge <pravin.shedge4linux@gmail.com>,
Vasyl Gomonovych <gomonovych@gmail.com>,
Wei Yongjun <weiyongjun1@huawei.com>
Subject: [GIT PULL] rpmsg updates for v4.16
Date: Mon, 5 Feb 2018 09:36:02 -0800 [thread overview]
Message-ID: <20180205173602.GZ17344@builder> (raw)
The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:
Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)
are available in the Git repository at:
git://github.com/andersson/remoteproc tags/rpmsg-v4.16
for you to fetch changes up to c3388a075c8ac568f892c40bec919ba8ac4077f0:
rpmsg: smd: Fix double unlock in __qcom_smd_send() (2018-01-19 07:04:33 -0800)
----------------------------------------------------------------
rpmsg updates for v4.16
This fixes a few issues found in the SMD and GLINK drivers and corrects the
handling of SMD channels that are found in an (previously) unexpected state.
----------------------------------------------------------------
Bjorn Andersson (6):
rpmsg: glink: smem: Ensure ordering during tx
rpmsg: smd: Perform handshake during open
rpmsg: smd: Create device for all channels
rpmsg: smd: Wake up all waiters
rpmsg: smd: Fail send on a closed channel
rpmsg: smd: Don't hold the tx lock during wait
Dan Carpenter (1):
rpmsg: smd: Fix double unlock in __qcom_smd_send()
Pravin Shedge (1):
drivers: rpmsg: remove duplicate includes
Vasyl Gomonovych (1):
remoteproc: qcom: Use PTR_ERR_OR_ZERO() in glink prob
Wei Yongjun (1):
rpmsg: glink: Fix missing mutex_init() in qcom_glink_alloc_channel()
drivers/remoteproc/qcom_common.c | 2 +-
drivers/rpmsg/qcom_glink_native.c | 1 +
drivers/rpmsg/qcom_glink_smem.c | 5 +--
drivers/rpmsg/qcom_smd.c | 66 +++++++++++++++++++++++++++++----------
4 files changed, 55 insertions(+), 19 deletions(-)
reply other threads:[~2018-02-05 17:36 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=20180205173602.GZ17344@builder \
--to=bjorn.andersson@linaro.org \
--cc=dan.carpenter@oracle.com \
--cc=gomonovych@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=pravin.shedge4linux@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=weiyongjun1@huawei.com \
/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