From: Bjorn Andersson <andersson@kernel.org>
To: swboyd@chromium.org, mathieu.poirier@linaro.org,
arnaud.pouliquen@foss.st.com, quic_bjorande@quicinc.com,
quic_clew@quicinc.com, Sarannya S <quic_sarannya@quicinc.com>
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V5 0/3] rpmsg signaling/flowcontrol patches
Date: Tue, 18 Apr 2023 09:09:47 -0700 [thread overview]
Message-ID: <168183418159.1484313.2492339947490878263.b4-ty@kernel.org> (raw)
In-Reply-To: <1681807721-32343-1-git-send-email-quic_sarannya@quicinc.com>
On Tue, 18 Apr 2023 14:18:38 +0530, Sarannya S wrote:
> Added new IOCTLS- RPMSG_GET_SIGNAL_IOCTL and RPMSG_SET_SIGNAL_IOCTL
> to get/set the rpmsg char device's flow control signal.
> Update the cmd name 'RPM_CMD_SIGNALS' to 'GLINK_CMD_SIGNALS'.
> Addressed review comments to change variable names/descriptions.
>
> Chris Lew (2):
> rpmsg: glink: Add support to handle signals command
> rpmsg: char: Add RPMSG GET/SET SIGNAL IOCTL support
>
> [...]
Applied, thanks!
[1/3] rpmsg: core: Add signal API support
commit: cc7c3bc62c6c74c217ea73e30a135fd2c3affb34
[2/3] rpmsg: glink: Add support to handle signals command
commit: 96a7a78517751f01c2a3aeef46768159aca370fd
[3/3] rpmsg: char: Add RPMSG GET/SET SIGNAL IOCTL support
commit: bdae2e497fd6cb1de0f142f3c64d89a38e3576e3
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
next prev parent reply other threads:[~2023-04-18 16:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-18 8:48 [PATCH V5 0/3] rpmsg signaling/flowcontrol patches Sarannya S
2023-04-18 8:48 ` [PATCH V5 1/3] rpmsg: core: Add signal API support Sarannya S
2023-04-19 9:53 ` Arnaud POULIQUEN
2023-04-19 20:37 ` Bjorn Andersson
2023-04-18 8:48 ` [PATCH V5 2/3] rpmsg: glink: Add support to handle signals command Sarannya S
2023-04-18 8:48 ` [PATCH V5 3/3] rpmsg: char: Add RPMSG GET/SET SIGNAL IOCTL support Sarannya S
2023-04-19 9:55 ` Arnaud POULIQUEN
2023-04-18 16:09 ` Bjorn Andersson [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-21 16:03 [PATCH V5 0/3] rpmsg signaling/flowcontrol patches Sarannya S
2023-02-28 19:42 ` Konrad Dybcio
2023-02-21 15:55 Sarannya S
2023-02-21 14:35 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=168183418159.1484313.2492339947490878263.b4-ty@kernel.org \
--to=andersson@kernel.org \
--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=quic_sarannya@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