From: Joe Perches <joe@perches.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Andy Whitcroft <apw@canonical.com>,
linux-media@vger.kernel.org, laurent.pinchart@ideasonboard.com,
hans@jjverkuil.nl
Subject: Re: [PATCH 1/1] checkpatch: Deprecate V4L2 pipeline power management code
Date: Tue, 14 Jul 2026 05:11:17 -0700 [thread overview]
Message-ID: <3e7b6acec459836275940908320db45a84f170b7.camel@perches.com> (raw)
In-Reply-To: <alYaJNtPID_c3eZn@kekkonen.localdomain>
On Tue, 2026-07-14 at 14:14 +0300, Sakari Ailus wrote:
> > Given this patch, checkpatch's message would be something like
> >
> "Deprecated use of 'v4l2_pipeline_pm_get', prefer '' instead"
>
> That's even technically correct: these functions serve no useful purpose
> anymore, all new drivers effectively use Runtime PM anyway.
OK, but given that there are only 32 uses in 16 files in all
of -next, why not just fix the uses then delete the functions?
$ git grep -P -w 'v4l2_pipeline_(?:link_notify|pm_get|pm_put)' | \
grep -vP '^(?:include|drivers/media/v4l2-core)' | \
wc -l
32
$ git grep -P -w -l 'v4l2_pipeline_(?:link_notify|pm_get|pm_put)' | \
grep -vP '^(?:include|drivers/media/v4l2-core)' | \
wc -l
16
> > > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > []
> > > @@ -879,6 +879,9 @@ our %deprecated_apis = (
> > > "DEFINE_IDR" => "DEFINE_XARRAY",
> > > "idr_init" => "xa_init",
> > > "idr_init_base" => "xa_init_flags",
> > > + "v4l2_pipeline_link_notify" => "",
> > > + "v4l2_pipeline_pm_get" => "",
> > > + "v4l2_pipeline_pm_put" => "",
> >
> > Add something like "v4l2 runtime power management API" instead
> > At least point out what that is.
>
> How about simply "Runtime PM"?
Better than nothing IMO.
next prev parent reply other threads:[~2026-07-14 12:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 16:13 Sakari Ailus
2026-07-14 8:15 ` Laurent Pinchart
2026-07-14 10:28 ` Joe Perches
2026-07-14 11:14 ` Sakari Ailus
2026-07-14 12:11 ` Joe Perches [this message]
2026-07-14 12:31 ` Sakari Ailus
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=3e7b6acec459836275940908320db45a84f170b7.camel@perches.com \
--to=joe@perches.com \
--cc=apw@canonical.com \
--cc=hans@jjverkuil.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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
all inboxes | Powered by JetHome®