From: Sarannya S <quic_sarannya@quicinc.com>
To: <quic_bjorande@quicinc.com>, <arnaud.pouliquen@foss.st.com>,
<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>,
Sarannya S <quic_sarannya@quicinc.com>
Subject: [PATCH V4 0/3] rpmsg signaling/flowcontrol patches
Date: Mon, 28 Nov 2022 23:32:52 +0530 [thread overview]
Message-ID: <1669658575-21993-1-git-send-email-quic_sarannya@quicinc.com> (raw)
[Change from V3]:
Fixed review comments in previous set.
Sarannya S (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 | 63 +++++++++++++++++++++++++++++++++++++++
drivers/rpmsg/rpmsg_char.c | 60 ++++++++++++++++++++++++++++++++-----
drivers/rpmsg/rpmsg_core.c | 20 +++++++++++++
drivers/rpmsg/rpmsg_internal.h | 2 ++
include/linux/rpmsg.h | 15 ++++++++++
5 files changed, 152 insertions(+), 8 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next reply other threads:[~2022-11-28 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 18:02 Sarannya S [this message]
2022-11-28 18:02 ` [PATCH V4 1/3] rpmsg: core: Add signal API support Sarannya S
2022-11-29 9:29 ` Arnaud POULIQUEN
2022-11-30 18:23 ` Mathieu Poirier
2022-12-01 11:27 ` Sarannya S
2022-11-28 18:02 ` [PATCH V4 2/3] rpmsg: glink: Add support to handle signals command Sarannya S
2022-11-28 18:02 ` [PATCH V4 3/3] rpmsg: char: Add TIOCMGET/TIOCMSET ioctl support Sarannya S
2022-11-30 3:00 ` [PATCH V4 0/3] rpmsg signaling/flowcontrol patches Bjorn Andersson
2022-12-07 13:04 Sarannya S
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=1669658575-21993-1-git-send-email-quic_sarannya@quicinc.com \
--to=quic_sarannya@quicinc.com \
--cc=arnaud.pouliquen@foss.st.com \
--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_bjorande@quicinc.com \
--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;
as well as URLs for NNTP newsgroup(s).