From: Deepak Kumar Singh <quic_deesin@quicinc.com>
To: <bjorn.andersson@linaro.org>, <swboyd@chromium.org>,
<quic_clew@quicinc.com>, <mathieu.poirier@linaro.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-remoteproc@vger.kernel.org>,
Deepak Kumar Singh <quic_deesin@quicinc.com>
Subject: [PATCH V2 0/3] rpmsg and glink signaling API support
Date: Wed, 19 Jan 2022 01:13:10 +0530 [thread overview]
Message-ID: <1642534993-6552-1-git-send-email-quic_deesin@quicinc.com> (raw)
[Change from V1]
Fixed most of the review comments in V1.
Deepak Kumar Singh (3):
rpmsg: core: Add signal API support
rpmsg: glink: Add support to handle signals command
rpmsg: char: Add TIOCMGET/TIOCMSET ioctl support
drivers/rpmsg/qcom_glink_native.c | 77 +++++++++++++++++++++++++++++++++++++++
drivers/rpmsg/rpmsg_char.c | 47 ++++++++++++++++++++++--
drivers/rpmsg/rpmsg_core.c | 21 +++++++++++
drivers/rpmsg/rpmsg_internal.h | 2 +
include/linux/rpmsg.h | 14 +++++++
5 files changed, 157 insertions(+), 4 deletions(-)
--
2.7.4
next reply other threads:[~2022-01-18 19:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 19:43 Deepak Kumar Singh [this message]
2022-01-18 19:43 ` [PATCH V2 1/3] rpmsg: core: Add signal " Deepak Kumar Singh
2022-03-11 21:11 ` Bjorn Andersson
2022-03-23 10:57 ` Arnaud POULIQUEN
2022-03-29 11:00 ` Deepak Kumar Singh
2022-04-01 13:23 ` Arnaud POULIQUEN
2022-01-18 19:43 ` [PATCH V2 2/3] rpmsg: glink: Add support to handle signals command Deepak Kumar Singh
2022-03-11 21:09 ` Bjorn Andersson
2022-03-23 7:20 ` Deepak Kumar Singh
2022-04-01 13:27 ` Arnaud POULIQUEN
2022-01-18 19:43 ` [PATCH V2 3/3] rpmsg: char: Add TIOCMGET/TIOCMSET ioctl support Deepak Kumar Singh
2022-03-23 13:38 ` Arnaud POULIQUEN
2022-03-29 12:25 ` Deepak Kumar Singh
2022-04-01 13:54 ` Arnaud POULIQUEN
2022-03-23 10:17 ` [PATCH V2 0/3] rpmsg and glink signaling API support Arnaud POULIQUEN
2022-04-25 8:59 ` Arnaud POULIQUEN
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=1642534993-6552-1-git-send-email-quic_deesin@quicinc.com \
--to=quic_deesin@quicinc.com \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=quic_clew@quicinc.com \
--cc=swboyd@chromium.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®