From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
Cc: Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
Bryan O'Donoghue <bryan.odonoghue@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.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-arm-msm@vger.kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/6] media: dt-bindings: media: qcom,sc8280xp-camss: Fix interrupt types
Date: Fri, 6 Sep 2024 14:43:43 +0200 [thread overview]
Message-ID: <5796baca-3347-44c7-8f0e-568c7177ec73@kernel.org> (raw)
In-Reply-To: <9f64102b-407d-482b-bd0b-b158fd7b255d@linaro.org>
On 06/09/2024 13:06, Vladimir Zapolskiy wrote:
> Hi Krzysztof,
>
> On 9/6/24 13:31, Krzysztof Kozlowski wrote:
>> On Thu, Sep 05, 2024 at 07:41:37PM +0300, Vladimir Zapolskiy wrote:
>>> The expected type of all CAMSS interrupts is edge rising, fix it in
>>> the documented example from CAMSS device tree bindings for sc8280xp.
>>
>> Subject: drop duplicated media. One media is enough (the first).
>>
>
> thank you for review, here I've attemted to follow the established practice.
>
> % git log -n 500 --oneline Documentation/devicetree/bindings/media/ | grep "media:.*media:" | wc -l
> 166
>
> So 1/3 of relevant commits to the folder have the duplicated "media:"
> in the subject, the reason is not totally clear to me, thus I've just
> inflowed into the same.
People like to repeat same mistakes, but just because 166 times someone
did a mistake, is not a reason to do the same.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-06 12:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 16:41 [PATCH 0/6] media: dt-bindings: media: camss: Fix interrupt types Vladimir Zapolskiy
2024-09-05 16:41 ` [PATCH 1/6] media: dt-bindings: media: qcom,sc8280xp-camss: " Vladimir Zapolskiy
2024-09-06 10:31 ` Krzysztof Kozlowski
2024-09-06 10:31 ` Krzysztof Kozlowski
2024-09-06 11:06 ` Vladimir Zapolskiy
2024-09-06 12:43 ` Krzysztof Kozlowski [this message]
2024-09-05 16:41 ` [PATCH 2/6] media: dt-bindings: media: qcom,sdm845-camss: " Vladimir Zapolskiy
2024-09-06 10:32 ` Krzysztof Kozlowski
2024-09-05 16:41 ` [PATCH 3/6] media: dt-bindings: media: qcom,sm8250-camss: " Vladimir Zapolskiy
2024-09-06 10:32 ` Krzysztof Kozlowski
2024-09-05 16:41 ` [PATCH 4/6] arm64: dts: qcom: sc8280xp: Fix interrupt type of camss interrupts Vladimir Zapolskiy
2024-09-06 11:12 ` Bryan O'Donoghue
2024-09-06 14:31 ` Johan Hovold
2024-09-06 21:42 ` Vladimir Zapolskiy
2024-09-05 16:41 ` [PATCH 5/6] arm64: dts: qcom: sdm845: Fix interrupt types " Vladimir Zapolskiy
2024-09-06 11:12 ` Bryan O'Donoghue
2024-09-05 16:41 ` [PATCH 6/6] arm64: dts: qcom: sm8250: " Vladimir Zapolskiy
2024-09-06 11:12 ` 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=5796baca-3347-44c7-8f0e-568c7177ec73@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rfoss@kernel.org \
--cc=robh@kernel.org \
--cc=todor.too@gmail.com \
--cc=vladimir.zapolskiy@linaro.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