lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 24 Aug 2023 16:34:41 +0300
From:   Laurent Pinchart <laurent.pinchart@...asonboard.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     Jack Zhu <jack.zhu@...rfivetech.com>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Robert Foss <rfoss@...nel.org>,
        Todor Tomov <todor.too@...il.com>, bryan.odonoghue@...aro.org,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Conor Dooley <conor+dt@...nel.org>,
        Philipp Zabel <p.zabel@...gutronix.de>,
        Hans Verkuil <hverkuil-cisco@...all.nl>,
        linux-media@...r.kernel.org, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org, linux-staging@...ts.linux.dev,
        changhuang.liang@...rfivetech.com
Subject: Re: [PATCH v8 0/8] Add StarFive Camera Subsystem driver

On Thu, Aug 24, 2023 at 03:08:33PM +0200, Greg Kroah-Hartman wrote:
> On Thu, Aug 24, 2023 at 08:23:33PM +0800, Jack Zhu wrote:
> > 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?

It's also customary to add a TODO file in the driver directory to list
the work needed before moving the code to drivers/media/. Jack, could
you please do so ?


-- 
Regards,

Laurent Pinchart

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ