From: Junjie Cao <junjie.cao@intel.com>
To: Manuel Knitza <manuel.knitza@googlemail.com>
Cc: Sergey Zagursky <gvozdoder@gmail.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Miguel Vadillo <miguel.vadillo@intel.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v3] media: ipu-bridge: do not use the CVS device lookup for IVSC
Date: Mon, 14 Sep 2026 17:36:29 +0800 [thread overview]
Message-ID: <20260914093629.639591-1-junjie.cao@intel.com> (raw)
In-Reply-To: <20260914074130.24756-1-manuel.knitza@googlemail.com>
On Mon, 14 Sep 2026 09:41:16 +0200, Manuel Knitza wrote:
> The driver is a hard dependency of the 7.2 CVS path,
> not an ancillary sub-driver, so hiding it behind
> MEDIA_HIDE_ANCILLARY_SUBDRV means distros silently ship
> a kernel whose bridge routes to a driver they cannot
> build.
Agreed, and it is already on the list ;)
https://lore.kernel.org/r/20260913125345.588586-1-junjie.cao@intel.com
With it, Arch's config gets VIDEO_INTEL_CVS=m on
olddefconfig. If you get a chance to confirm the same
on a linux-ptl build, a Tested-by there would be much
appreciated.
next prev parent reply other threads:[~2026-09-14 9:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 21:15 [PATCH v3] media: ipu-bridge: do not use the CVS device lookup for IVSC Sergey Zagursky
2026-09-12 18:58 ` Manuel Knitza
2026-09-13 9:37 ` Junjie Cao
2026-09-13 12:59 ` Junjie Cao
2026-09-14 7:41 ` Manuel Knitza
2026-09-14 9:36 ` Junjie Cao [this message]
2026-09-14 4:32 ` Thorsten Leemhuis
2026-09-14 10:11 ` 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=20260914093629.639591-1-junjie.cao@intel.com \
--to=junjie.cao@intel.com \
--cc=gvozdoder@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=manuel.knitza@googlemail.com \
--cc=miguel.vadillo@intel.com \
--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