From: Rui Miguel Silva <rui.silva@linaro.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Rui Miguel Silva <rui.silva@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Hans Verkuil <hverkuil@xs4all.nl>,
Rob Herring <robh+dt@kernel.org>,
linux-media <linux-media@vger.kernel.org>,
Fabio Estevam <fabio.estevam@nxp.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Ryan Harkin <ryan.harkin@linaro.org>
Subject: Re: [PATCH 0/4] media: ov2680: follow up from initial version
Date: Tue, 08 May 2018 14:52:58 +0100 [thread overview]
Message-ID: <m3muxa6ypx.fsf@linaro.org> (raw)
In-Reply-To: <CAOMZO5APU9CTGukYsQarPCvp=e8P6LgOWbNFx-dhnKM_3UHf+A@mail.gmail.com>
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
> <rui.silva@linaro.org> 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:
<snip>
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
next prev parent reply other threads:[~2018-05-08 13:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 15:56 [PATCH 0/4] media: ov2680: follow up from initial version Rui Miguel Silva
2018-05-07 15:56 ` [PATCH 1/4] media: ov2680: dt: add voltage supplies as required Rui Miguel Silva
2018-05-07 15:56 ` [PATCH 2/4] media: ov2680: dt: rename gpio to reset and fix polarity Rui Miguel Silva
2018-05-07 15:56 ` [PATCH 3/4] media: ov2680: rename powerdown gpio " Rui Miguel Silva
2018-05-07 15:56 ` [PATCH 4/4] media: ov2680: add regulators to supply control Rui Miguel Silva
2018-05-08 13:29 ` [PATCH 0/4] media: ov2680: follow up from initial version Fabio Estevam
2018-05-08 13:52 ` Rui Miguel Silva [this message]
2018-05-08 13:55 ` Fabio Estevam
2018-05-08 20:03 ` Sakari Ailus
2018-05-09 11:03 ` Rui Miguel Silva
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=m3muxa6ypx.fsf@linaro.org \
--to=rui.silva@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=festevam@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=ryan.harkin@linaro.org \
--cc=sakari.ailus@linux.intel.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).