From: Bjorn Andersson <andersson@kernel.org>
To: Sarannya S <quic_sarannya@quicinc.com>
Cc: quic_bjorande@quicinc.com, arnaud.pouliquen@foss.st.com,
swboyd@chromium.org, quic_clew@quicinc.com,
mathieu.poirier@linaro.org, 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>,
Richard Cochran <richardcochran@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
"moderated list:ARM64 PORT (AARCH64 ARCHITECTURE)"
<linux-arm-kernel@lists.infradead.org>,
"open list:PTP HARDWARE CLOCK SUPPORT" <netdev@vger.kernel.org>,
"open list:XDP (eXpress Data Path)" <bpf@vger.kernel.org>
Subject: Re: [PATCH V5 1/3] rpmsg: core: Add signal API support
Date: Tue, 21 Feb 2023 09:20:52 -0800 [thread overview]
Message-ID: <20230221172052.papcj7wl3u5gzo6s@ripper> (raw)
In-Reply-To: <1676990114-1369-2-git-send-email-quic_sarannya@quicinc.com>
On Tue, Feb 21, 2023 at 08:05:12PM +0530, 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>
> Signed-off-by: Sarannya S <quic_sarannya@quicinc.com>
> ---
> arch/arm64/boot/Image.gz-dtb | Bin 0 -> 12413735 bytes
> drivers/rpmsg/rpmsg_core.c | 20 ++++++++++++++++++++
> drivers/rpmsg/rpmsg_core.c.rej | 11 +++++++++++
> drivers/rpmsg/rpmsg_internal.h | 2 ++
> include/linux/rpmsg.h | 15 +++++++++++++++
Looks like you accidentally included the Image.gz-dtb and .rej file in
the patch. Please resend without these.
Thanks,
Bjorn
> 5 files changed, 48 insertions(+)
> create mode 100644 arch/arm64/boot/Image.gz-dtb
> create mode 100644 drivers/rpmsg/rpmsg_core.c.rej
next prev parent reply other threads:[~2023-02-21 17:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 14:35 [PATCH V5 0/3] rpmsg signaling/flowcontrol patches Sarannya S
2023-02-21 14:35 ` [PATCH V5 2/3] rpmsg: glink: Add support to handle signals command Sarannya S
2023-02-21 14:35 ` [PATCH V5 3/3] rpmsg: char: Add TIOCMGET/TIOCMSET ioctl support Sarannya S
[not found] ` <1676990114-1369-2-git-send-email-quic_sarannya@quicinc.com>
2023-02-21 17:20 ` Bjorn Andersson [this message]
2023-02-21 15:55 [PATCH V5 0/3] rpmsg signaling/flowcontrol patches Sarannya S
2023-02-21 15:56 ` [PATCH V5 1/3] rpmsg: core: Add signal API support Sarannya S
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-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
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=20230221172052.papcj7wl3u5gzo6s@ripper \
--to=andersson@kernel.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.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=mathieu.poirier@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=quic_bjorande@quicinc.com \
--cc=quic_clew@quicinc.com \
--cc=quic_deesin@quicinc.com \
--cc=quic_sarannya@quicinc.com \
--cc=richardcochran@gmail.com \
--cc=swboyd@chromium.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
all inboxes | Powered by JetHome®