From: Jai Luthra <jai.luthra@ideasonboard.com>
To: Conor Dooley <conor@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Changhuang Liang <changhuang.liang@starfivetech.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Rishikesh Donadkar <r-donadkar@ti.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: Re: [PATCH v3 2/2] media: dt-bindings: Drop starfive,jh7110-camss from staging
Date: Mon, 20 Apr 2026 18:23:11 +0530 [thread overview]
Message-ID: <177668959135.489396.16825302864805843232@freya> (raw)
In-Reply-To: <20260420-very-cartel-645595ffd1c7@spud>
Hi Conor,
Quoting Conor Dooley (2026-04-20 16:46:11)
> On Tue, Mar 03, 2026 at 02:54:07PM +0530, Jai Luthra wrote:
> > The starfive-camss driver is no longer being worked upon for destaging,
> > and will be dropped in a subsequent commit, so drop the DT bindings.
> >
> > Link: https://lore.kernel.org/all/ZQ0PR01MB13024A92926C415C187D2C18F29F2@ZQ0PR01MB1302.CHNPR01.prod.partner.outlook.cn/
> > Acked-by: Changhuang Liang <changhuang.liang@starfivetech.com>
> > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> > Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> > Signed-off-by: Jai Luthra <jai.luthra@ideasonboard.com>
>
> In removing the binding, you should have also sent patches for removing
> the users of this:
> arch/riscv/boot/dts/starfive/jh7110-deepcomputing-fml13v01.dtb: /soc/isp@19840000: failed to match any schema with compatible: ['starfive,jh7110-camss']
> arch/riscv/boot/dts/starfive/jh7110-pine64-star64.dtb: /soc/isp@19840000: failed to match any schema with compatible: ['starfive,jh7110-camss']
> arch/riscv/boot/dts/starfive/jh7110-milkv-mars.dtb: /soc/isp@19840000: failed to match any schema with compatible: ['starfive,jh7110-camss']
> arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2-lite.dtb: /soc/isp@19840000: failed to match any schema with compatible: ['starfive,jh7110-camss']
> arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2-lite-emmc.dtb: /soc/isp@19840000: failed to match any schema with compatible: ['starfive,jh7110-camss']
> arch/riscv/boot/dts/starfive/jh7110-milkv-marscm-emmc.dtb: /soc/isp@19840000: failed to match any schema with compatible: ['starfive,jh7110-camss']
> arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2-v1.2a.dtb: /soc/isp@19840000: failed to match any schema with compatible: ['starfive,jh7110-camss']
> arch/riscv/boot/dts/starfive/jh7110-orangepi-rv.dtb: /soc/isp@19840000: failed to match any schema with compatible: ['starfive,jh7110-camss']
> arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2-v1.3b.dtb: /soc/isp@19840000: failed to match any schema with compatible: ['starfive,jh7110-camss']
> arch/riscv/boot/dts/starfive/jh7110-milkv-marscm-lite.dtb: /soc/isp@19840000: failed to match any schema with compatible: ['starfive,jh7110-camss']
My bad, I'll post a patch.
Ideally the usage should have been removed in a separate patch before this
one that drops the bindings. But what would be best now? Have "Fixes: <this
commit>" in the patch dropping the uses, so it can be picked in rc2?
Thanks,
Jai
prev parent reply other threads:[~2026-04-20 12:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 9:24 [PATCH v3 0/2] media: staging: Drop StarFive JH7110 Camera Subsystem Jai Luthra
2026-03-03 9:24 ` [PATCH v3 1/2] media: staging: Drop starfive-camss from staging Jai Luthra
2026-03-03 9:24 ` [PATCH v3 2/2] media: dt-bindings: Drop starfive,jh7110-camss " Jai Luthra
2026-04-20 11:16 ` Conor Dooley
2026-04-20 12:53 ` Jai Luthra [this message]
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=177668959135.489396.16825302864805843232@freya \
--to=jai.luthra@ideasonboard.com \
--cc=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=r-donadkar@ti.com \
--cc=robh@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