From: jacopo mondi <jacopo@jmondi.org>
To: Akinobu Mita <akinobu.mita@gmail.com>
Cc: linux-media@vger.kernel.org,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
"H . Nikolaus Schaller" <hns@goldelico.com>,
Hugues Fruchet <hugues.fruchet@st.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v3 0/3] media: ov9650: support device tree probing
Date: Sun, 21 Jan 2018 17:33:14 +0100 [thread overview]
Message-ID: <20180121163314.GN24926@w540> (raw)
In-Reply-To: <1516547656-3879-1-git-send-email-akinobu.mita@gmail.com>
Hello Akinobu,
On Mon, Jan 22, 2018 at 12:14:13AM +0900, Akinobu Mita wrote:
> This patchset adds device tree probing for ov9650 driver. This contains
> an actual driver change and a newly added binding documentation part.
>
> * Changelog v3
> - Add Reviewed-by: tags
> - Add MAINTAINERS entry
>
> * Changelog v2
> - Split binding documentation, suggested by Rob Herring and Jacopo Mondi
> - Improve the wording for compatible property in the binding documentation,
> suggested by Jacopo Mondi
> - Improve the description for the device node in the binding documentation,
> suggested by Sakari Ailus
> - Remove ov965x_gpio_set() helper and open-code it, suggested by Jacopo Mondi
> and Sakari Ailus
> - Call clk_prepare_enable() in s_power callback instead of probe, suggested
> by Sakari Ailus
> - Unify clk and gpio configuration in a single if-else block and, also add
> a check either platform data or fwnode is actually specified, suggested
> by Jacopo Mondi
> - Add CONFIG_OF guards, suggested by Jacopo Mondi
>
> Akinobu Mita (3):
> media: ov9650: support device tree probing
> media: MAINTAINERS: add entry for ov9650 driver
> media: ov9650: add device tree binding
As you've closed my comments on v1/v2, for driver and device tree bindings:
Reviewed-by: Jacopo Mondi <jacopo+renesas@jmondi.org>
No need to resend just to add the tags, but in case you have to, please
add them.
Thanks
j
>
> .../devicetree/bindings/media/i2c/ov9650.txt | 36 ++++++
> MAINTAINERS | 10 ++
> drivers/media/i2c/ov9650.c | 130 +++++++++++++++------
> 3 files changed, 138 insertions(+), 38 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/media/i2c/ov9650.txt
>
> Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>
> Cc: Jacopo Mondi <jacopo@jmondi.org>
> Cc: H. Nikolaus Schaller <hns@goldelico.com>
> Cc: Hugues Fruchet <hugues.fruchet@st.com>
> Cc: Sakari Ailus <sakari.ailus@linux.intel.com>
> Cc: Mauro Carvalho Chehab <mchehab@s-opensource.com>
> Cc: Rob Herring <robh@kernel.org>
> --
> 2.7.4
>
next prev parent reply other threads:[~2018-01-21 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 15:14 [PATCH v3 0/3] media: ov9650: support device tree probing Akinobu Mita
2018-01-21 15:14 ` [PATCH v3 1/3] " Akinobu Mita
2018-01-21 15:14 ` [PATCH v3 2/3] media: MAINTAINERS: add entry for ov9650 driver Akinobu Mita
2018-01-25 12:05 ` Sylwester Nawrocki
2018-01-21 15:14 ` [PATCH v3 3/3] media: ov9650: add device tree binding Akinobu Mita
2018-01-21 16:33 ` jacopo mondi [this message]
2018-01-25 11:55 ` [PATCH v3 0/3] media: ov9650: support device tree probing 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=20180121163314.GN24926@w540 \
--to=jacopo@jmondi.org \
--cc=akinobu.mita@gmail.com \
--cc=hns@goldelico.com \
--cc=hugues.fruchet@st.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@s-opensource.com \
--cc=robh@kernel.org \
--cc=s.nawrocki@samsung.com \
--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