From: Tommaso Merciai <tommaso.merciai@amarulasolutions.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
linuxfancy@googlegroups.com, linux-amarula@amarulasolutions.com,
quentin.schulz@theobroma-systems.com,
Jacopo Mondi <jacopo@jmondi.org>,
Daniel Scally <djrscally@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 5/6] media: dt-bindings: ov5693: document YAML binding
Date: Thu, 30 Jun 2022 12:09:57 +0200 [thread overview]
Message-ID: <20220630100957.GE482517@tom-ThinkPad-T14s-Gen-2i> (raw)
In-Reply-To: <Yr1xzeqW2p4jVDzS@valkosipuli.retiisi.eu>
Hi Sakari,
On Thu, Jun 30, 2022 at 12:50:05PM +0300, Sakari Ailus wrote:
> Hi Tommaso,
>
> On Thu, Jun 30, 2022 at 11:16:13AM +0200, Tommaso Merciai wrote:
> > Hi Sakari,
> >
> > On Thu, Jun 30, 2022 at 12:12:47PM +0300, Sakari Ailus wrote:
> > > On Thu, Jun 30, 2022 at 11:02:32AM +0200, Tommaso Merciai wrote:
> > > > On Thu, Jun 30, 2022 at 10:07:19AM +0200, Krzysztof Kozlowski wrote:
> > > > > On 30/06/2022 09:45, Tommaso Merciai wrote:
> > > > > > Add documentation of device tree in YAML schema for the OV5693
> > > > > > CMOS image sensor from Omnivision
> > > > > >
> > > > > > Signed-off-by: Tommaso Merciai <tommaso.merciai@amarulasolutions.com>
> > > > > > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > > > > > Reviewed-by: Sakari Ailus <sakari.ailus@iki.fi>
> > > > >
> > > > > How Sakari's tag appeared here? There was no email from him.
> > > >
> > > > Sakari made me some review on v2, but I think he forgot to add the mailing
> > > > list in cc. ( I suppose :) )
> > > >
> > > > Let me know if I need to remove this.
> > >
> > > You're only supposed to put these tags into patches if you get them in
> > > written form as part of the review, signalling acceptance of the patch in
> > > various forms. Just commenting a patch does not imply this.
> > >
> > > Please also see Documentation/process/submitting-patches.rst for more
> > > information on how to use the tags.
> >
> > Thanks for sharing this. My bad.
> > I remove your tags.
>
> The patches themselves seem fine. I'd just drop the 4th patch or at least
> come up with a better name for ov5693_hwcfg() --- you're acquiring
> resources there, and that generally fits well for probe. The code is fine
> already.
Then we don't need v5 with your reviewed tags removed?
I think the patch4 is needed to add dts support properly.
Also this contains devm_clk_get_optional fix suggested by Jacopo and
support for ACPI-based platforms that specify the clock frequency by
using the "clock-frequency" property instead of specifying a clock
provider reference.
Some suggestion on the function name?
Thanks,
Tommaso
>
> --
> Sakari Ailus
--
Tommaso Merciai
Embedded Linux Engineer
tommaso.merciai@amarulasolutions.com
__________________________________
Amarula Solutions SRL
Via Le Canevare 30, 31100 Treviso, Veneto, IT
T. +39 042 243 5310
info@amarulasolutions.com
www.amarulasolutions.com
next prev parent reply other threads:[~2022-06-30 10:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220630074525.481790-1-tommaso.merciai@amarulasolutions.com>
2022-06-30 7:45 ` [PATCH v4 5/6] media: dt-bindings: ov5693: document YAML binding Tommaso Merciai
2022-06-30 8:07 ` Krzysztof Kozlowski
2022-06-30 9:02 ` Tommaso Merciai
2022-06-30 9:12 ` Sakari Ailus
2022-06-30 9:16 ` Tommaso Merciai
2022-06-30 9:50 ` Sakari Ailus
2022-06-30 10:09 ` Tommaso Merciai [this message]
2022-06-30 10:15 ` Daniel Scally
2022-06-30 11:21 ` Sakari Ailus
2022-06-30 13:56 ` Tommaso Merciai
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=20220630100957.GE482517@tom-ThinkPad-T14s-Gen-2i \
--to=tommaso.merciai@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=djrscally@gmail.com \
--cc=jacopo@jmondi.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-amarula@amarulasolutions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linuxfancy@googlegroups.com \
--cc=mchehab@kernel.org \
--cc=quentin.schulz@theobroma-systems.com \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
/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).