From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Jason Chen <jason.z.chen@intel.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/4] media: dt-bindings: Add OmniVision OV08X40
Date: Wed, 2 Oct 2024 09:32:17 +0100 [thread overview]
Message-ID: <6823b53c-a352-47b4-adc3-7ecbe2bcd819@linaro.org> (raw)
In-Reply-To: <lbfppnit7d4mkstrlbxgtemjhdu7yno3kjwb7pyfaees6y7v4v@imoqfze6i36r>
On 02/10/2024 07:20, Krzysztof Kozlowski wrote:
>> + assigned-clocks: true
>> + assigned-clock-parents: true
>> + assigned-clock-rates: true
> Drop all three, redundant.
Ah, I understand.
Ack.
---
bod
next prev parent reply other threads:[~2024-10-02 8:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 13:15 [PATCH v2 0/4] ov08x40: Enable use of ov08x40 on Qualcomm X1E80100 CRD Bryan O'Donoghue
2024-10-01 13:15 ` [PATCH v2 1/4] media: ov08x40: Fix burst write sequence Bryan O'Donoghue
2024-10-01 13:15 ` [PATCH v2 2/4] media: dt-bindings: Add OmniVision OV08X40 Bryan O'Donoghue
2024-10-01 13:22 ` Sakari Ailus
2024-10-01 13:47 ` Bryan O'Donoghue
2024-10-02 6:22 ` Krzysztof Kozlowski
2024-10-02 6:20 ` Krzysztof Kozlowski
2024-10-02 8:32 ` Bryan O'Donoghue [this message]
2024-10-01 13:15 ` [PATCH v2 3/4] media: ov08x40: Rename ext_clk to xvclk Bryan O'Donoghue
2024-10-01 13:15 ` [PATCH v2 4/4] media: ov08x40: Add OF probe support Bryan O'Donoghue
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=6823b53c-a352-47b4-adc3-7ecbe2bcd819@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jason.z.chen@intel.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=senozhatsky@chromium.org \
/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
all inboxes | Powered by JetHome®