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 2/3] media: m2m-deinterlace: remove unused struct 'vb2_dc_conf'
Date: Thu, 30 May 2024 14:26:18 +0100	[thread overview]
Message-ID: <20240530132619.71103-3-linux@treblig.org> (raw)
In-Reply-To: <20240530132619.71103-1-linux@treblig.org>

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

'vb2_dc_conf' has been unused since the original
commit 8f0755c06b90 ("[media] media: Add mem2mem deinterlacing driver").

Remove it.

Signed-off-by: Dr. David Alan Gilbert <linux@treblig.org>
---
 drivers/media/platform/m2m-deinterlace.c | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/drivers/media/platform/m2m-deinterlace.c b/drivers/media/platform/m2m-deinterlace.c
index 96b35a5d6174..5adcef80c698 100644
--- a/drivers/media/platform/m2m-deinterlace.c
+++ b/drivers/media/platform/m2m-deinterlace.c
@@ -724,10 +724,6 @@ static const struct v4l2_ioctl_ops deinterlace_ioctl_ops = {
 /*
  * Queue operations
  */
-struct vb2_dc_conf {
-	struct device           *dev;
-};
-
 static int deinterlace_queue_setup(struct vb2_queue *vq,
 				unsigned int *nbuffers, unsigned int *nplanes,
 				unsigned int sizes[], struct device *alloc_devs[])
-- 
2.45.1


  parent 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 [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 ` linux [this message]
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-3-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.