From: Rui Miguel Silva <rmfrfs@gmail.com>
To: Rob Herring <robh@kernel.org>
Cc: Rui Miguel Silva <rui.silva@linaro.org>,
mchehab@kernel.org, sakari.ailus@linux.intel.com,
hverkuil@xs4all.nl, linux-media@vger.kernel.org,
Fabio Estevam <fabio.estevam@nxp.com>,
Ryan Harkin <ryan.harkin@linaro.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v6 1/2] media: ov2680: dt: Add bindings for OV2680
Date: Fri, 18 May 2018 16:27:21 +0100 [thread overview]
Message-ID: <m3in7lrnl2.fsf@gmail.com> (raw)
In-Reply-To: <20180518141830.GA14547@rob-hp-laptop>
Hi Rob,
On Fri 18 May 2018 at 14:18, Rob Herring wrote:
> On Wed, May 09, 2018 at 03:31:58PM +0100, Rui Miguel Silva
> wrote:
>> Add device tree binding documentation for the OV2680 camera
>> sensor.
>>
>> CC: devicetree@vger.kernel.org
>> Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
>> ---
>> .../devicetree/bindings/media/i2c/ov2680.txt | 46
>> +++++++++++++++++++
>> 1 file changed, 46 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/media/i2c/ov2680.txt
>
> Please add acks/reviewed bys on new versions.
I have add this to the cover letter [0]:
- Removed Rob Herring Reviewed-by tag, since bindings have changed
since his
ack.
But only now I notice that I did not CC the devicetree list for
the all
series, but only for this particular patch. Sorry about that.
---
Cheers,
Rui
[0]: https://www.spinics.net/lists/linux-media/msg133942.html
next prev parent reply other threads:[~2018-05-18 15:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 14:31 [PATCH v6 0/2] media: Introduce Omnivision OV2680 driver Rui Miguel Silva
2018-05-09 14:31 ` [PATCH v6 1/2] media: ov2680: dt: Add bindings for OV2680 Rui Miguel Silva
2018-05-18 14:18 ` Rob Herring
2018-05-18 15:27 ` Rui Miguel Silva [this message]
2018-05-23 20:04 ` Rob Herring
2018-05-09 14:31 ` [PATCH v6 2/2] media: ov2680: Add Omnivision OV2680 sensor driver Rui Miguel Silva
2018-06-26 14:25 ` Sakari Ailus
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=m3in7lrnl2.fsf@gmail.com \
--to=rmfrfs@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=rui.silva@linaro.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 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.