From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Sarannya S <quic_sarannya@quicinc.com>,
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
Subject: Re: [PATCH V5 0/3] rpmsg signaling/flowcontrol patches
Date: Tue, 28 Feb 2023 20:42:15 +0100 [thread overview]
Message-ID: <b280c6a5-04dc-8a4f-459c-4703e567fa1d@linaro.org> (raw)
In-Reply-To: <1676995418-19358-1-git-send-email-quic_sarannya@quicinc.com>
On 21.02.2023 17:03, Sarannya S wrote:
> Added two new RPMSG IOCTLs for rpmsg_char- RPMSG_GET_SIGNAL_IOCTRL and
> RPMSG_SET_SIGNAL_IOCTRL, to set/get the flow.
> Addressed review comments for changing variable names/ desciptions.
>
Hi, your changes mostly don't apply on -next-20230228, please rebase
them. Not sure if I didn't miss anything, but I did it locally to test
this [1]. My Wi-Fi chip on SM6375 seems to send quite some signals calls
and applying this series got rid of "unhandled rx cmd: 15" and the
corresponding timeouts.
Also, please consider using b4 [2] for sending patches, you only sent
them to a couple of people and it didn't even reach patchwork..
Konrad
[1] https://github.com/SoMainline/linux/commits/signals_rebase
[2] https://b4.docs.kernel.org/en/latest/contributor/overview.html
> Sarannya S (3):
> rpmsg: core: Add signal API support
> rpmsg: glink: Add support to handle signals command
> rpmsg: char: Add RPMSG GET/SET SIGNAL IOCTL support
>
> drivers/rpmsg/qcom_glink_native.c | 63 +++++++++++++++++++++++++++++++++++++++
> drivers/rpmsg/rpmsg_char.c | 58 ++++++++++++++++++++++++++++++-----
> drivers/rpmsg/rpmsg_core.c | 20 +++++++++++++
> drivers/rpmsg/rpmsg_internal.h | 2 ++
> include/linux/rpmsg.h | 15 ++++++++++
> include/uapi/linux/rpmsg.h | 12 +++++++-
> 6 files changed, 162 insertions(+), 8 deletions(-)
>
next prev parent reply other threads:[~2023-02-28 19:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 16:03 [PATCH V5 0/3] rpmsg signaling/flowcontrol patches Sarannya S
2023-02-21 16:03 ` [PATCH V5 1/3] rpmsg: core: Add signal API support Sarannya S
2023-02-21 16:03 ` [PATCH V5 2/3] rpmsg: glink: Add support to handle signals command Sarannya S
2023-02-21 16:03 ` [PATCH V5 3/3] rpmsg: char: Add RPMSG GET/SET SIGNAL IOCTL support Sarannya S
2023-02-28 19:42 ` Konrad Dybcio [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-18 8:48 [PATCH V5 0/3] rpmsg signaling/flowcontrol patches Sarannya S
2023-04-18 16:09 ` Bjorn Andersson
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=b280c6a5-04dc-8a4f-459c-4703e567fa1d@linaro.org \
--to=konrad.dybcio@linaro.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