From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Miguel Vadillo <miguel.vadillo@intel.com>
Cc: linux-media@vger.kernel.org, wei.a.xu@intel.com,
atul.raut@intel.com, antti.laakso@linux.intel.com,
mehdi.djait@linux.intel.com, kieran.bingham@ideasonboard.com
Subject: Re: [PATCH v4 0/3] media: i2c: cvs: Add Intel CVS driver
Date: Tue, 26 May 2026 18:53:28 +0300 [thread overview]
Message-ID: <ahXB-Eg1O2-PlFvU@kekkonen.localdomain> (raw)
In-Reply-To: <20260526022509.162908-1-miguel.vadillo@intel.com>
Hi Miguel,
On Mon, May 25, 2026 at 07:25:05PM -0700, Miguel Vadillo wrote:
> Cover Letter
> ------------
>
> This patch series introduces support for Intel Computer Vision Sensing
> (CVS) devices found on Intel Luna Lake (LNL), Panther Lake (PTL), and
> Arrow Lake (ARL) platforms.
Thanks for the update. I got from Media CI:
drivers/media/i2c/cvs/core.c:909:12: warning: ‘cvs_resume’ defined but not used [-Wunused-function]
909 | static int cvs_resume(struct device *dev)
| ^~~~~~~~~~
drivers/media/i2c/cvs/core.c:892:12: warning: ‘cvs_suspend’ defined but not used [-Wunused-function]
892 | static int cvs_suspend(struct device *dev)
| ^~~~~~~~~~~
I suppose this happens when CONFIG_PM isn't defined
<URL:https://gitlab.freedesktop.org/linux-media/users/sailus/-/jobs/100763316/artifacts/file/artifacts/no-PM.config>?
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2026-05-26 15:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 2:25 [PATCH v4 0/3] media: i2c: cvs: Add Intel CVS driver Miguel Vadillo
2026-05-26 2:25 ` [PATCH v4 1/3] media: i2c: cvs: Add driver of Intel Computer Vision Sensing Controller(CVS) Miguel Vadillo
2026-05-26 2:25 ` [PATCH v4 2/3] media: pci: intel: Add CVS support for IPU bridge driver Miguel Vadillo
2026-05-26 2:25 ` [PATCH v4 3/3] ACPI: scan: Honor _DEP for Intel CVS devices Miguel Vadillo
2026-05-26 15:53 ` Sakari Ailus [this message]
2026-05-26 16:29 ` [PATCH v4 0/3] media: i2c: cvs: Add Intel CVS driver Vadillo, Miguel
2026-05-27 9:01 ` Sakari Ailus
2026-05-27 14:23 ` Vadillo, Miguel
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=ahXB-Eg1O2-PlFvU@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=antti.laakso@linux.intel.com \
--cc=atul.raut@intel.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mehdi.djait@linux.intel.com \
--cc=miguel.vadillo@intel.com \
--cc=wei.a.xu@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 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.