From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Shreeya Patel <shreeya.patel@collabora.com>,
Heiko Stuebner <heiko@sntech.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
jose.abreu@synopsys.com, nelson.costa@synopsys.com,
shawn.wen@rock-chips.com, nicolas.dufresne@collabora.com,
Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: kernel@collabora.com, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: [PATCH v1 0/3] Remove unused code from HDMI RX driver
Date: Thu, 6 Mar 2025 11:05:30 +0300 [thread overview]
Message-ID: <20250306080533.294964-1-dmitry.osipenko@collabora.com> (raw)
Hi Hans,
This is a follow up to the v13 HDMI RX patches [1] addressing warning
produced by Intel's test robot.
It also removes the unused HDMI CODEC leftovers that we accidentally
missed to remove previously and makes minor improvement to the definition
of struct snps_hdmirx_dev, all of which I noticed while was looking at
the warning report.
Dmitry Osipenko (3):
media: platform: synopsys: hdmirx: Remove duplicated header inclusion
media: platform: synopsys: hdmirx: Remove unused HDMI audio CODEC
relics
media: platform: synopsys: hdmirx: Optimize struct snps_hdmirx_dev
drivers/media/platform/synopsys/hdmirx/snps_hdmirx.c | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
--
2.48.1
next reply other threads:[~2025-03-06 8:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 8:05 Dmitry Osipenko [this message]
2025-03-06 8:05 ` [PATCH v1 1/3] media: platform: synopsys: hdmirx: Remove duplicated header inclusion Dmitry Osipenko
2025-03-06 8:05 ` [PATCH v1 2/3] media: platform: synopsys: hdmirx: Remove unused HDMI audio CODEC relics Dmitry Osipenko
2025-03-06 8:05 ` [PATCH v1 3/3] media: platform: synopsys: hdmirx: Optimize struct snps_hdmirx_dev Dmitry Osipenko
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=20250306080533.294964-1-dmitry.osipenko@collabora.com \
--to=dmitry.osipenko@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=hverkuil@xs4all.nl \
--cc=jose.abreu@synopsys.com \
--cc=kernel@collabora.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=nelson.costa@synopsys.com \
--cc=nicolas.dufresne@collabora.com \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=shawn.wen@rock-chips.com \
--cc=shreeya.patel@collabora.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