From: Frank Li <Frank.Li@nxp.com>
To: Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Rui Miguel Silva <rmfrfs@gmail.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Martin Kepplinger-Novakovic <martink@posteo.de>,
Purism Kernel Team <kernel@puri.sm>
Cc: linux-media@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Frank Li <Frank.Li@nxp.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>
Subject: [PATCH v4 0/4] media: platform: nxp: Trivial cleanup pathces
Date: Fri, 16 Jan 2026 11:29:18 -0500 [thread overview]
Message-ID: <20260116-cam_cleanup-v4-0-29ce01640443@nxp.com> (raw)
Some trivial patch to reduce goto at probe functions.
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
Changes in v4:
- collect alex's review tag
- fix grammer in error message
- Link to v3: https://lore.kernel.org/r/20251215-cam_cleanup-v3-0-a61995068f38@nxp.com
Changes in v3:
- rebase to v6.19-rc1
- avoid use __free() == NULL according to cleanup.h
- Link to v2: https://lore.kernel.org/r/20251119-cam_cleanup-v2-0-df732cc83ff1@nxp.com
Changes in v2:
- add new patch media: nxp: Add dev_err_probe() to all error paths in *async_register() helpers
- detail change see each patch's change log.
- Link to v1: https://lore.kernel.org/r/20251117-cam_cleanup-v1-0-6cd42872db79@nxp.com
---
Frank Li (4):
media: nxp: use dev_err_probe() to simplify code
media: nxp: imx8-isi: use devm_pm_runtime_enable() to simplify code
media: nxp: use cleanup __free(fwnode_handle) simplify code
media: nxp: Add dev_err_probe() to all error paths in *async_register() helpers
drivers/media/platform/nxp/imx-mipi-csis.c | 54 +++++++--------
drivers/media/platform/nxp/imx7-media-csi.c | 14 ++--
.../media/platform/nxp/imx8-isi/imx8-isi-core.c | 16 ++---
drivers/media/platform/nxp/imx8mq-mipi-csi2.c | 77 ++++++++++------------
4 files changed, 71 insertions(+), 90 deletions(-)
---
base-commit: 49cc7b5d0dee386c44b51a90eb49037b2a1f5b2e
change-id: 20250807-cam_cleanup-b6d90ba9dac3
Best regards,
--
Frank Li <Frank.Li@nxp.com>
next reply other threads:[~2026-01-16 16:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 16:29 Frank Li [this message]
2026-01-16 16:29 ` [PATCH v4 1/4] media: nxp: use dev_err_probe() to simplify code Frank Li
2026-01-16 16:29 ` [PATCH v4 2/4] media: nxp: imx8-isi: use devm_pm_runtime_enable() " Frank Li
2026-01-21 1:43 ` Laurent Pinchart
2026-01-16 16:29 ` [PATCH v4 3/4] media: nxp: use cleanup __free(fwnode_handle) " Frank Li
2026-01-21 1:45 ` Laurent Pinchart
2026-01-16 16:29 ` [PATCH v4 4/4] media: nxp: Add dev_err_probe() to all error paths in *async_register() helpers Frank Li
2026-01-21 1:51 ` Laurent Pinchart
2026-01-21 1:55 ` [PATCH v4 0/4] media: platform: nxp: Trivial cleanup pathces Laurent Pinchart
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=20260116-cam_cleanup-v4-0-29ce01640443@nxp.com \
--to=frank.li@nxp.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=kernel@puri.sm \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=martink@posteo.de \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=rmfrfs@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.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