From: Mathieu Poirier <mathieu.poirier@linaro.org>
To: linux@treblig.org
Cc: arnaud.pouliquen@foss.st.com, andersson@kernel.org,
corbet@lwn.net, linux-remoteproc@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] rpmsg: Remove unused method pointers *send_offchannel
Date: Tue, 29 Apr 2025 13:01:07 -0600 [thread overview]
Message-ID: <aBEh85gDlaEywWtX@p14s> (raw)
In-Reply-To: <20250424142746.79062-4-linux@treblig.org>
Hi,
On Thu, Apr 24, 2025 at 03:27:46PM +0100, linux@treblig.org wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
> After the previous patch, there are no implementers of the
> send_offchannel() and trysend_offchannel() methods.
>
> Remove them.
>
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> ---
> drivers/rpmsg/rpmsg_internal.h | 6 ------
> 1 file changed, 6 deletions(-)
>
> diff --git a/drivers/rpmsg/rpmsg_internal.h b/drivers/rpmsg/rpmsg_internal.h
> index 42c7007be1b5..397e4926bd02 100644
> --- a/drivers/rpmsg/rpmsg_internal.h
> +++ b/drivers/rpmsg/rpmsg_internal.h
> @@ -50,10 +50,8 @@ struct rpmsg_device_ops {
> * @destroy_ept: see @rpmsg_destroy_ept(), required
> * @send: see @rpmsg_send(), required
> * @sendto: see @rpmsg_sendto(), optional
> - * @send_offchannel: see @rpmsg_send_offchannel(), optional
> * @trysend: see @rpmsg_trysend(), required
> * @trysendto: see @rpmsg_trysendto(), optional
> - * @trysend_offchannel: see @rpmsg_trysend_offchannel(), optional
> * @poll: see @rpmsg_poll(), optional
> * @set_flow_control: see @rpmsg_set_flow_control(), optional
> * @get_mtu: see @rpmsg_get_mtu(), optional
> @@ -67,13 +65,9 @@ struct rpmsg_endpoint_ops {
>
> int (*send)(struct rpmsg_endpoint *ept, void *data, int len);
> int (*sendto)(struct rpmsg_endpoint *ept, void *data, int len, u32 dst);
> - int (*send_offchannel)(struct rpmsg_endpoint *ept, u32 src, u32 dst,
> - void *data, int len);
>
> int (*trysend)(struct rpmsg_endpoint *ept, void *data, int len);
> int (*trysendto)(struct rpmsg_endpoint *ept, void *data, int len, u32 dst);
> - int (*trysend_offchannel)(struct rpmsg_endpoint *ept, u32 src, u32 dst,
> - void *data, int len);
> __poll_t (*poll)(struct rpmsg_endpoint *ept, struct file *filp,
> poll_table *wait);
> int (*set_flow_control)(struct rpmsg_endpoint *ept, bool pause, u32 dst);
I'm good with this patchset. Can you fix the last paragraph in the comment for
function rpmsg_send_offchannel_raw() and remove the reference to "_offchannel"?
Thanks,
Mathieu
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-04-29 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 14:27 [PATCH v2 0/3] rpmsg offchannel deadcoding linux
2025-04-24 14:27 ` [PATCH v2 1/3] rpmsg: core: Remove deadcode linux
2025-04-24 14:27 ` [PATCH v2 2/3] rpmsg: virtio: Remove uncallable offchannel functions linux
2025-04-24 14:27 ` [PATCH v2 3/3] rpmsg: Remove unused method pointers *send_offchannel linux
2025-04-29 19:01 ` Mathieu Poirier [this message]
2025-04-29 20:15 ` Dr. David Alan Gilbert
2025-04-29 23:47 ` Dr. David Alan Gilbert
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=aBEh85gDlaEywWtX@p14s \
--to=mathieu.poirier@linaro.org \
--cc=andersson@kernel.org \
--cc=arnaud.pouliquen@foss.st.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=linux@treblig.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).