From: "Thierry Reding" <thierry.reding@gmail.com>
To: <linux@treblig.org>, <mchehab@kernel.org>, <ming.qian@nxp.com>,
<eagle.zhou@nxp.com>, <digetx@gmail.com>, <jonathanh@nvidia.com>
Cc: <linux-tegra@vger.kernel.org>, <linux-media@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] media: tegra-vde: remove unused struct 'tegra_vde_h264_frame'
Date: Thu, 30 May 2024 16:59:32 +0200 [thread overview]
Message-ID: <D1N2H4X8ZL1D.18140DCI2SH8X@gmail.com> (raw)
In-Reply-To: <20240530132619.71103-4-linux@treblig.org>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
On Thu May 30, 2024 at 3:26 PM CEST, wrote:
> From: "Dr. David Alan Gilbert" <linux@treblig.org>
>
> 'tegra_vde_h264_frame' has been unused since
> commit 313db7d235a0 ("media: staging: tegra-vde: Remove legacy UAPI
> support").
>
> Remove it.
>
> Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
> ---
> drivers/media/platform/nvidia/tegra-vde/h264.c | 5 -----
> drivers/media/platform/nvidia/tegra-vde/vde.h | 1 -
> 2 files changed, 6 deletions(-)
Not that you really need it, but since I'm here:
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-05-30 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-30 13:26 [PATCH v2 0/3] Dead structs in media/platform linux
2024-05-30 13:26 ` [PATCH v2 1/3] media: amphion: remove unused struct 'vpu_malone_frame_buffer' linux
2024-05-30 13:26 ` [PATCH v2 2/3] media: m2m-deinterlace: remove unused struct 'vb2_dc_conf' linux
2024-05-30 13:26 ` [PATCH v2 3/3] media: tegra-vde: remove unused struct 'tegra_vde_h264_frame' linux
2024-05-30 14:59 ` Thierry Reding [this message]
2024-05-30 15:28 ` 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=D1N2H4X8ZL1D.18140DCI2SH8X@gmail.com \
--to=thierry.reding@gmail.com \
--cc=digetx@gmail.com \
--cc=eagle.zhou@nxp.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mchehab@kernel.org \
--cc=ming.qian@nxp.com \
/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