All of lore.kernel.org
 help / color / mirror / Atom feed
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 07:16:19 +0100	[thread overview]
Message-ID: <2023110730-thousand-skyrocket-d6ba@gregkh> (raw)
In-Reply-To: <2023110745-tableful-trapezoid-4206@gregkh>

On Tue, Nov 07, 2023 at 07:15:10AM +0100, Greg Kroah-Hartman wrote:
> On Tue, Nov 07, 2023 at 11:27:27AM +0800, Jack Zhu wrote:
> > 
> > 
> > On 2023/10/31 9:09, Jack Zhu wrote:
> > > 
> > > 
> > > On 2023/10/25 11:14, Jack Zhu wrote:
> > >> Hi,
> > >> 
> > >> This series is the v11 series that attempts to support the Camera Subsystem
> > >> found on StarFive JH7110 SoC.
> > > 
> > > Hi Hans and Laurent,
> > > 
> > > Could you please help review the code?
> > > Thank you for your time!
> > > 
> > 
> > Hi,
> > 
> > Could you please take some time to help review the code? Thank you so much!
> 
> It is the middle of the merge window, no new code can be added to any
> maintainers tree at this point in time, please relax there is no rush or
> deadline at all here.
> 
> While you wait, why not help out and review other patch submissions from
> other developers, which will help your changes get to the top of the
> queue?  That way everyone's load is reduced and you are not just asking
> for others to do work for you with nothing in return.

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?

thanks,

greg k-h

  reply	other threads:[~2023-11-07  6:16 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 [this message]
2023-11-07  8:05         ` Jack Zhu
2023-11-07  8:27           ` Greg Kroah-Hartman
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=2023110730-thousand-skyrocket-d6ba@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.