From: Arnaud POULIQUEN <arnaud.pouliquen@foss.st.com>
To: <linux@treblig.org>, <andersson@kernel.org>,
<mathieu.poirier@linaro.org>
Cc: <corbet@lwn.net>, <linux-remoteproc@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] rpmsg offchannel deadcoding
Date: Wed, 30 Apr 2025 09:11:44 +0200 [thread overview]
Message-ID: <723fd0a2-c1c0-4a3d-8f48-2913c0206729@foss.st.com> (raw)
In-Reply-To: <20250429234600.301083-1-linux@treblig.org>
On 4/30/25 01:45, linux@treblig.org wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
> Hi,
> This removes a couple of unused functions in rpmsg,
> and (v2) after discussions with Arnaud, follows the thread
> and removes code that they would call.
Acked-by: Arnaud Pouliquen <arnaud.pouliquen@foss.st.com>
Thanks,
Arnaud
>
> (Build tested only)
>
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
>
> V3
> Fixup comment on rpmsg_send_offchannel_raw(),
> removing the reference to "_offchannel" - as per Mathieu's
> review
>
> Dr. David Alan Gilbert (3):
> rpmsg: core: Remove deadcode
> rpmsg: virtio: Remove uncallable offchannel functions
> rpmsg: Remove unused method pointers *send_offchannel
>
> Documentation/staging/rpmsg.rst | 46 -----------------------
> drivers/rpmsg/rpmsg_core.c | 63 --------------------------------
> drivers/rpmsg/rpmsg_internal.h | 6 ---
> drivers/rpmsg/virtio_rpmsg_bus.c | 24 +-----------
> include/linux/rpmsg.h | 22 -----------
> 5 files changed, 1 insertion(+), 160 deletions(-)
>
next prev parent reply other threads:[~2025-04-30 7:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 23:45 linux
2025-04-29 23:45 ` [PATCH v3 1/3] rpmsg: core: Remove deadcode linux
2025-04-29 23:45 ` [PATCH v3 2/3] rpmsg: virtio: Remove uncallable offchannel functions linux
2025-04-29 23:45 ` [PATCH v3 3/3] rpmsg: Remove unused method pointers *send_offchannel linux
2025-04-30 7:11 ` Arnaud POULIQUEN [this message]
2025-05-06 17:27 ` [PATCH v3 0/3] rpmsg offchannel deadcoding Mathieu Poirier
2025-05-06 17:57 ` 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=723fd0a2-c1c0-4a3d-8f48-2913c0206729@foss.st.com \
--to=arnaud.pouliquen@foss.st.com \
--cc=andersson@kernel.org \
--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 \
--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
all inboxes | Powered by JetHome®