From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: References: <20180507155655.1555-1-rui.silva@linaro.org> From: Rui Miguel Silva Subject: Re: [PATCH 0/4] media: ov2680: follow up from initial version In-reply-to: Date: Tue, 08 May 2018 14:52:58 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; format=flowed To: Fabio Estevam Cc: Rui Miguel Silva , Mauro Carvalho Chehab , Sakari Ailus , Hans Verkuil , Rob Herring , linux-media , Fabio Estevam , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Ryan Harkin List-ID: Ola Fabio, On Tue 08 May 2018 at 13:29, Fabio Estevam wrote: > Hi Rui, > > On Mon, May 7, 2018 at 12:56 PM, Rui Miguel Silva > wrote: >> Sorry I have Out-of-Office some part of last week, I had v6 of >> the original >> series ready but since I have received the notification from >> patchwork that the >> v5 was accepted, I am sending this as a follow up tha address >> Fabio comments. >> >> - this adds the power supplies to this sensor >> - fix gpio polarity and naming. >> >> Cheers, >> Rui >> >> >> Rui Miguel Silva (4): >> media: ov2680: dt: add voltage supplies as required >> media: ov2680: dt: rename gpio to reset and fix polarity >> media: ov2680: rename powerdown gpio and fix polarity >> media: ov2680: add regulators to supply control > > As the initial ov2680 series has not been applied, I think it > would be > better if you send a new version with all these fixes. What I've got was this from patchwork: Hello, The following patches (submitted by you) have been updated in patchwork: * linux-media: [v5,1/2] media: ov2680: dt: Add bindings for OV2680 - http://patchwork.linuxtv.org/patch/48819/ - for: Linux Media kernel patches was: New now: Accepted * linux-media: [v4,1/2] media: ov2680: dt: Add bindings for OV2680 - http://patchwork.linuxtv.org/patch/48357/ - for: Linux Media kernel patches was: New now: Accepted This email is a notification only - you do not need to respond. - Patches submitted to linux-media@vger.kernel.org have the following possible states: Accepted: when some driver maintainer says that the patch will be applied via his tree, or when everything is ok and it got applied either at the main tree or via some other tree (fixes tree; some other maintainer's tree - when it belongs to other subsystems, etc); So, my understand is that the patches will be applied or are already applied to someone tree (strange patchwork does not send who or which tree), but since I do not want to break someone workflow I will wait for some maintainer word on this... If it is better to send the original series or the follow up patches. Thanks for your feedback. --- Cheers, Rui