From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Arun Kumar Neelakantam <aneela@codeaurora.org>
Cc: ohad@wizery.com, clew@codeaurora.org, sricharan@codeaurora.org,
linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 1/4] rpmsg: core: Add signal API support
Date: Fri, 5 Oct 2018 12:22:57 -0700 [thread overview]
Message-ID: <20181005192257.GB12063@builder> (raw)
In-Reply-To: <1538722776-13648-2-git-send-email-aneela@codeaurora.org>
On Thu 04 Oct 23:59 PDT 2018, Arun Kumar Neelakantam wrote:
> diff --git a/drivers/rpmsg/rpmsg_core.c b/drivers/rpmsg/rpmsg_core.c
[..]
> +/**
> + * rpmsg_get_signals() - get the signals for this endpoint
> + * @ept: the rpmsg endpoint
> + *
> + * Returns 0 on success and an appropriate error value on failure.
I like the fact that you're using the return value to pass the bits, but
the comment doesn't reflect this - and you don't handle this properly in
the TIOCMGET case in patch 3.
> + */
> +int rpmsg_get_signals(struct rpmsg_endpoint *ept)
> +{
> + if (WARN_ON(!ept))
> + return -EINVAL;
> + if (!ept->ops->get_signals)
> + return -EOPNOTSUPP;
> +
> + return ept->ops->get_signals(ept);
> +}
> +EXPORT_SYMBOL(rpmsg_get_signals);
Apart from that the series looks good.
Regards,
Bjorn
next prev parent reply other threads:[~2018-10-05 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-05 6:59 [PATCH V3 0/4] Add TIOCM Signals support for RPMSG char devices Arun Kumar Neelakantam
2018-10-05 6:59 ` [PATCH V3 1/4] rpmsg: core: Add signal API support Arun Kumar Neelakantam
2018-10-05 19:22 ` Bjorn Andersson [this message]
2018-10-05 6:59 ` [PATCH V3 2/4] rpmsg: glink: Add support to handle signals command Arun Kumar Neelakantam
2018-10-05 6:59 ` [PATCH V3 3/4] rpmsg: char: Add TIOCMGET/TIOCMSET ioctl support Arun Kumar Neelakantam
2018-10-05 6:59 ` [PATCH V3 4/4] rpmsg: char: Add signal callback and POLLPRI support Arun Kumar Neelakantam
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=20181005192257.GB12063@builder \
--to=bjorn.andersson@linaro.org \
--cc=aneela@codeaurora.org \
--cc=clew@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=ohad@wizery.com \
--cc=sricharan@codeaurora.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