All of lore.kernel.org
 help / color / mirror / Atom feed
From: linux@treblig.org
To: 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,
	"Dr. David Alan Gilbert" <linux@treblig.org>
Subject: [PATCH v2 0/3] Dead structs in media/platform
Date: Thu, 30 May 2024 14:26:16 +0100	[thread overview]
Message-ID: <20240530132619.71103-1-linux@treblig.org> (raw)

From: "Dr. David Alan Gilbert" <linux@treblig.org>

Clean out a bunch of dead structs in media/platform.
Build tested only.

Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>

v2:
  Removed tegra_vde_h264_frame declaration in header
  Typo in first subject line

Dr. David Alan Gilbert (3):
  media: amphion: remove unused struct 'vpu_malone_frame_buffer'
  media: m2m-deinterlace: remove unused struct 'vb2_dc_conf'
  media: tegra-vde: remove unused struct 'tegra_vde_h264_frame'

 drivers/media/platform/amphion/vpu_malone.c    | 5 -----
 drivers/media/platform/m2m-deinterlace.c       | 4 ----
 drivers/media/platform/nvidia/tegra-vde/h264.c | 5 -----
 drivers/media/platform/nvidia/tegra-vde/vde.h  | 1 -
 4 files changed, 15 deletions(-)

-- 
2.45.1


             reply	other threads:[~2024-05-30 13:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-30 13:26 linux [this message]
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
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=20240530132619.71103-1-linux@treblig.org \
    --to=linux@treblig.org \
    --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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.