From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Jai Luthra <jai.luthra@ideasonboard.com>,
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>,
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
Subject: Re: [PATCH v2 1/2] media: dt-bindings: Drop starfive,jh7110-camss from staging
Date: Sun, 18 Jan 2026 10:27:39 +0200 [thread overview]
Message-ID: <20260118082739.GA20659@pendragon.ideasonboard.com> (raw)
In-Reply-To: <8881acaf-3233-44a3-aa55-bb1236a7cc91@kernel.org>
On Sat, Jan 17, 2026 at 12:38:21PM +0100, Krzysztof Kozlowski wrote:
> On 17/01/2026 12:36, Krzysztof Kozlowski wrote:
> > On Fri, Jan 16, 2026 at 12:36:58PM +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.
> >
> > That's a moderately new SoC and commit was added ~2 years ago. Why is
> > this being dropped exactly?
>
> OK, the link below gives some answer but isn't this better just to mark
> it orphan and keep for some time? Is the driver working/useful? Maybe
> someone will volunteer for it?
It's in staging, nobody has registered any interest, the company behind
the hardware as publicly said they won't continue development, and
there's no documentation. I think that meets the bar for dropping the
driver. In the very unlikely case someone would want to revive it, the
source code will live in git history.
> >> Link: https://lore.kernel.org/all/ZQ0PR01MB13024A92926C415C187D2C18F29F2@ZQ0PR01MB1302.CHNPR01.prod.partner.outlook.cn/
> >> Acked-by: Changhuang Liang <changhuang.liang@starfivetech.com>
> >> Signed-off-by: Jai Luthra <jai.luthra@ideasonboard.com>
> >
> > Reverting/dropping changes is always in reverse of introducing them, so
> > this must be second commit. Otherwise your change is non-bisectable and
> > you have now warnings of undocumented ABI.
We can easily do that when applying.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2026-01-18 8:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 7:06 [PATCH v2 0/2] media: staging: Drop StarFive JH7110 Camera Subsystem Jai Luthra
2026-01-16 7:06 ` [PATCH v2 1/2] media: dt-bindings: Drop starfive,jh7110-camss from staging Jai Luthra
2026-01-17 11:36 ` Krzysztof Kozlowski
2026-01-17 11:38 ` Krzysztof Kozlowski
2026-01-18 8:27 ` Laurent Pinchart [this message]
2026-01-18 10:10 ` Krzysztof Kozlowski
2026-01-16 7:06 ` [PATCH v2 2/2] media: staging: Drop starfive-camss " Jai Luthra
2026-01-16 7:14 ` Changhuang Liang
2026-01-18 8:29 ` [PATCH v2 0/2] media: staging: Drop StarFive JH7110 Camera Subsystem 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=20260118082739.GA20659@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jai.luthra@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--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