From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Lee Jones <lee.jones@linaro.org>
Cc: Deepak Kumar Singh <deesin@codeaurora.org>,
Chris Lew <clew@codeaurora.org>,
Mathieu <mathieu.poirier@linaro.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
linux-remoteproc@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V7 0/4] Signaling api support in glink/rpmsg clients
Date: Wed, 7 Jul 2021 10:56:37 -0500 [thread overview]
Message-ID: <YOXOtRSpKO5WdlHZ@yoga> (raw)
In-Reply-To: <CAF2Aj3gAqjVbcMayR7yYBb6UxY5ekC9gdhpmNdz1-zLwo10yLw@mail.gmail.com>
On Tue 06 Jul 10:27 CDT 2021, Lee Jones wrote:
> On Wed, 2 Sept 2020 at 17:25, Deepak Kumar Singh <deesin@codeaurora.org>
> wrote:
>
> > Change from version 6
> > In last series(v6) i had put wrong version(v5) for cover note.
> > Which led to confusion for patch set series.
> >
> > In this series i have updated the label for cover letter(v7).
> > There is no change in patches. Only cover note label is updated.
> >
> > Change from version 5
> > [V6,4/4] rpmsg: char: Add signal callback and POLLPRI support
> > Updated for sparse warning. Replaced POLLPRI => EPOLLPRI to fix
> > warning.
> >
> > Change from version 4
> > I am taking over these patches from aneela@codeaurora.org
> > Fixed all the trivial review comments.
> >
> > Signal conversion to and from native signal as done in patch V4,2/4
> > is intentional.
> >
> > Arun Kumar Neelakantam (3):
> > rpmsg: glink: Add support to handle signals command
> > rpmsg: char: Add TIOCMGET/TIOCMSET ioctl support
> > rpmsg: char: Add signal callback and POLLPRI support
> >
> > Deepak Kumar Singh (1):
> > rpmsg: core: Add signal API support
> >
> > drivers/rpmsg/qcom_glink_native.c | 125
> > ++++++++++++++++++++++++++++++++++++++
> > drivers/rpmsg/rpmsg_char.c | 76 ++++++++++++++++++++++-
> > drivers/rpmsg/rpmsg_core.c | 40 ++++++++++++
> > drivers/rpmsg/rpmsg_internal.h | 5 ++
> > include/linux/rpmsg.h | 27 ++++++++
> > 5 files changed, 270 insertions(+), 3 deletions(-)
> >
> > --
> > The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> > a Linux Foundation Collaborative Project
> >
> >
> Any idea why this died at v7?
>
I had some concerns about the actual users of this and wanted the API to
be more generic. Deepak brought this up again recently and I think we
have a common understanding of how v8 should look like.
Regards,
Bjorn
next prev parent reply other threads:[~2021-07-07 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 16:24 [PATCH V7 0/4] Signaling api support in glink/rpmsg clients Deepak Kumar Singh
2020-09-02 16:24 ` [PATCH V7 1/4] rpmsg: core: Add signal API support Deepak Kumar Singh
2020-09-02 16:24 ` [PATCH V7 2/4] rpmsg: glink: Add support to handle signals command Deepak Kumar Singh
2020-09-02 16:24 ` [PATCH V7 3/4] rpmsg: char: Add TIOCMGET/TIOCMSET ioctl support Deepak Kumar Singh
2020-09-02 16:24 ` [PATCH V7 4/4] rpmsg: char: Add signal callback and POLLPRI support Deepak Kumar Singh
[not found] ` <CAF2Aj3gAqjVbcMayR7yYBb6UxY5ekC9gdhpmNdz1-zLwo10yLw@mail.gmail.com>
2021-07-07 15:56 ` Bjorn Andersson [this message]
2021-07-08 11:20 ` [PATCH V7 0/4] Signaling api support in glink/rpmsg clients Lee Jones
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=YOXOtRSpKO5WdlHZ@yoga \
--to=bjorn.andersson@linaro.org \
--cc=clew@codeaurora.org \
--cc=deesin@codeaurora.org \
--cc=lee.jones@linaro.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 \
/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