From: Jack Zhu <jack.zhu@starfivetech.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
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 v8 0/8] Add StarFive Camera Subsystem driver
Date: Fri, 25 Aug 2023 17:57:58 +0800 [thread overview]
Message-ID: <109d69d1-bd64-9157-da6b-a099dbe700fe@starfivetech.com> (raw)
In-Reply-To: <2023082416-flanking-requisite-a8ed@gregkh>
On 2023/8/24 21:08, Greg Kroah-Hartman wrote:
> On Thu, Aug 24, 2023 at 08:23:33PM +0800, Jack Zhu wrote:
>> Hi Greg,
>>
>> On 2023/8/24 19:37, Greg Kroah-Hartman wrote:
>> > On Thu, Aug 24, 2023 at 04:01:01PM +0800, Jack Zhu wrote:
>> >> Hi,
>> >>
>> >> This series is the v8 series that attempts to support the Camera Subsystem
>> >> found on StarFive JH7110 SoC.
>> >
>> > I don't see anything here about why this is in drivers/staging/media/
>> > now and not just in drivers/media/. What is preventing this to be put
>> > into the correct place to start with? What needs to be done to the code
>> > to get it out of drivers/staging/media/ and who is going to do that
>> > work?
>> >
>>
>> The series does not contain 3A interface. According to Laurent's suggestion,
>> we put the driver in the staging directory first. In the next stage, we will
>> continue to submit the 3A interface in the way of incremental development,
>> and finally expect the code to be placed in the drivers/media/.
>
> Can you please say that in the changelog text for when you are adding
> the driver so that we know this?
>
Yes, will do it. Thank you for your suggestion!
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2023-08-25 9:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-24 8:01 [PATCH v8 0/8] Add StarFive Camera Subsystem driver Jack Zhu
2023-08-24 8:01 ` [PATCH v8 1/8] media: dt-bindings: Add JH7110 Camera Subsystem Jack Zhu
2023-08-24 8:01 ` [PATCH v8 2/8] media: admin-guide: Add starfive_camss.rst for Starfive " Jack Zhu
2023-08-24 8:01 ` [PATCH v8 3/8] media: staging: media: starfive: camss: Add core driver Jack Zhu
2023-08-24 18:31 ` Christophe JAILLET
2023-08-25 10:44 ` Jack Zhu
2023-08-25 21:44 ` Christophe JAILLET
2023-08-30 10:41 ` Hans Verkuil
2023-08-30 10:44 ` Hans Verkuil
2023-08-24 8:01 ` [PATCH v8 4/8] media: staging: media: starfive: camss: Add video driver Jack Zhu
2023-08-24 8:01 ` [PATCH v8 5/8] media: staging: media: starfive: camss: Add ISP driver Jack Zhu
2023-08-24 8:01 ` [PATCH v8 6/8] media: staging: media: starfive: camss: Add capture driver Jack Zhu
2023-08-24 8:01 ` [PATCH v8 7/8] media: staging: media: starfive: camss: Add interrupt handling Jack Zhu
2023-08-24 8:01 ` [PATCH v8 8/8] media: staging: media: starfive: camss: Register devices Jack Zhu
2023-08-24 11:37 ` [PATCH v8 0/8] Add StarFive Camera Subsystem driver Greg Kroah-Hartman
2023-08-24 12:23 ` Jack Zhu
2023-08-24 13:08 ` Greg Kroah-Hartman
2023-08-24 13:34 ` Laurent Pinchart
2023-08-25 9:56 ` Jack Zhu
2023-08-25 9:57 ` Jack Zhu [this message]
2023-08-30 10:30 ` Hans Verkuil
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=109d69d1-bd64-9157-da6b-a099dbe700fe@starfivetech.com \
--to=jack.zhu@starfivetech.com \
--cc=bryan.odonoghue@linaro.org \
--cc=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--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).