[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20231123135354.GE16377@pendragon.ideasonboard.com>
Date: Thu, 23 Nov 2023 15:53:54 +0200
From: Laurent Pinchart <laurent.pinchart@...asonboard.com>
To: Umang Jain <umang.jain@...asonboard.com>
Cc: Greg KH <gregkh@...uxfoundation.org>, linux-media@...r.kernel.org,
kernel-list@...pberrypi.com, linux-kernel@...r.kernel.org,
linux-rpi-kernel@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
linux-staging@...ts.linux.dev,
Dave Stevenson <dave.stevenson@...pberrypi.com>,
"Ricardo B . Marliere" <ricardo@...liere.net>,
Dan Carpenter <error27@...il.com>,
Stefan Wahren <stefan.wahren@...e.com>
Subject: Re: [PATCH] fixup! staging: vc04_services: bcm2835-isp: Add a more
complex ISP processing component
On Thu, Nov 23, 2023 at 12:56:07PM +0000, Greg KH wrote:
> On Mon, Nov 13, 2023 at 09:07:55AM -0500, Umang Jain wrote:
> > Setup DMA Mask
> > ---
> > I realised while (re)creating the test branches (sent in reply to the cover
> > letter), I missed to squash this hunk in
> > "staging: vc04_services: bcm2835-isp: Add a more complex ISP processing component"
> > before sending out the series.
> >
> > Sending it as a fixup! for now.
>
> What does that mean? What can I do with this?
Umang, we don't do that for upstream kernel development. If a patch
needs a new version, you should send a new version. In some subsystems
maintainers will prefer if you only resubmit the offending patch when
the series is large (as a "vN.1" instead of a vN+1), while in other
cases resending the whole series is preferred.
Greg, I don't think Umang wanted you to do anything with this patch :-)
This was meant to tell reviewer that the issue was known already.
--
Regards,
Laurent Pinchart
Powered by blists - more mailing lists