From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Jack Zhu <jack.zhu@starfivetech.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
bryan.odonoghue@linaro.org, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-staging@lists.linux.dev,
changhuang.liang@starfivetech.com
Subject: Re: [PATCH v11 0/9] Add StarFive Camera Subsystem driver
Date: Tue, 7 Nov 2023 09:27:34 +0100 [thread overview]
Message-ID: <2023110756-alto-stream-eb92@gregkh> (raw)
In-Reply-To: <a2dbb182-2573-4c86-7e18-319d26a6593c@starfivetech.com>
On Tue, Nov 07, 2023 at 04:05:11PM +0800, Jack Zhu wrote:
> > Also, while you wait, why not just finish off the last 3 items on the
> > TODO list which would make your code not be required to go into the
> > staging portion of the tree at all? You've had a few weeks now, what is
> > preventing that from happening, and when will that work actually be
> > done?
> >
>
> One of my colleagues is doing related development, but he also has other
> projects at the same time, so he cannot devote all his efforts to this
> development. And we expect to use libcamera, which may take some time.
So that means there is no real plan at all to get this out of the
staging directory? If so, why should we take it at all as obviously
this means that the code is now abandoned?
confused,
greg k-h
next prev parent reply other threads:[~2023-11-07 8:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 3:14 [PATCH v11 0/9] Add StarFive Camera Subsystem driver Jack Zhu
2023-10-25 3:14 ` [PATCH v11 1/9] media: dt-bindings: Add JH7110 Camera Subsystem Jack Zhu
2023-10-25 3:14 ` [PATCH v11 2/9] media: admin-guide: Add starfive_camss.rst for Starfive " Jack Zhu
2023-10-25 3:14 ` [PATCH v11 3/9] media: staging: media: starfive: camss: Add core driver Jack Zhu
2023-10-25 3:14 ` [PATCH v11 4/9] media: staging: media: starfive: camss: Add video driver Jack Zhu
2023-10-25 3:14 ` [PATCH v11 5/9] media: staging: media: starfive: camss: Add ISP driver Jack Zhu
2023-10-25 3:14 ` [PATCH v11 6/9] media: staging: media: starfive: camss: Add capture driver Jack Zhu
2023-10-25 3:14 ` [PATCH v11 7/9] media: staging: media: starfive: camss: Add interrupt handling Jack Zhu
2023-10-25 3:14 ` [PATCH v11 8/9] media: staging: media: starfive: camss: Register devices Jack Zhu
2023-10-25 3:14 ` [PATCH v11 9/9] media: staging: media: starfive: camss: Add TODO file Jack Zhu
2023-10-31 1:09 ` [PATCH v11 0/9] Add StarFive Camera Subsystem driver Jack Zhu
2023-11-07 3:27 ` Jack Zhu
2023-11-07 6:15 ` Greg Kroah-Hartman
2023-11-07 6:16 ` Greg Kroah-Hartman
2023-11-07 8:05 ` Jack Zhu
2023-11-07 8:27 ` Greg Kroah-Hartman [this message]
2023-11-07 9:29 ` Jack Zhu
2023-11-07 10:09 ` 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=2023110756-alto-stream-eb92@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bryan.odonoghue@linaro.org \
--cc=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jack.zhu@starfivetech.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--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=rfoss@kernel.org \
--cc=robh+dt@kernel.org \
--cc=todor.too@gmail.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;
as well as URLs for NNTP newsgroup(s).