From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Sarannya S <quic_sarannya@quicinc.com>,
bjorn.andersson@linaro.org, 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,
Deepak Kumar Singh <quic_deesin@quicinc.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Shawn Guo <shawnguo@kernel.org>, Arnd Bergmann <arnd@arndb.de>,
Marcel Ziswiler <marcel.ziswiler@toradex.com>,
Vinod Koul <vkoul@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Mark Brown <broonie@kernel.org>,
"moderated list:ARM64 PORT (AARCH64 ARCHITECTURE)"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH V4 1/3] rpmsg: core: Add signal API support
Date: Mon, 28 Nov 2022 14:33:31 +0100 [thread overview]
Message-ID: <51555970-5287-0c8e-0169-9ecc1aa85f48@linaro.org> (raw)
In-Reply-To: <6b445991-0843-6a1e-1bd0-1980a78a0481@linaro.org>
On 28/11/2022 14:32, Krzysztof Kozlowski wrote:
> On 28/11/2022 14:28, Sarannya S wrote:
>> Some transports like Glink support the state notifications between
>> clients using flow control signals similar to serial protocol signals.
>> Local glink client drivers can send and receive flow control status
>> to glink clients running on remote processors.
>>
>> Add APIs to support sending and receiving of flow control status by
>> rpmsg clients.
>>
>> Signed-off-by: Deepak Kumar Singh <quic_deesin@quicinc.com>
>> ---
One more problem - SoB does not match From field, so DCO chain is broken
here.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-28 13:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 13:28 [PATCH V4 1/3] rpmsg: core: Add signal API support Sarannya S
2022-11-28 13:28 ` [PATCH V4 2/3] rpmsg: glink: Add support to handle signals command Sarannya S
2022-11-28 13:28 ` [PATCH V4 3/3] rpmsg: char: Add TIOCMGET/TIOCMSET ioctl support Sarannya S
2022-11-28 13:32 ` [PATCH V4 1/3] rpmsg: core: Add signal API support Krzysztof Kozlowski
2022-11-28 13:33 ` Krzysztof Kozlowski [this message]
2022-11-28 16:38 ` Mathieu Poirier
2022-11-28 18:02 [PATCH V4 0/3] rpmsg signaling/flowcontrol patches Sarannya S
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-12-07 13:04 [PATCH V4 0/3] rpmsg signaling/flowcontrol patches Sarannya S
2022-12-07 13:04 ` [PATCH V4 1/3] rpmsg: core: Add signal API support Sarannya S
2022-12-21 16:12 ` Arnaud POULIQUEN
2022-12-27 15:32 ` Bjorn Andersson
2023-01-03 13:50 ` Arnaud POULIQUEN
2023-01-04 16:30 ` Bjorn Andersson
2023-01-04 18:31 ` 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=51555970-5287-0c8e-0169-9ecc1aa85f48@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=mathieu.poirier@linaro.org \
--cc=quic_clew@quicinc.com \
--cc=quic_deesin@quicinc.com \
--cc=quic_sarannya@quicinc.com \
--cc=shawnguo@kernel.org \
--cc=swboyd@chromium.org \
--cc=vkoul@kernel.org \
--cc=will@kernel.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).