From: Krzysztof Kozlowski <krzk@kernel.org>
To: Gatien CHEVALLIER <gatien.chevallier@foss.st.com>,
alexandre.torgue@foss.st.com, robh+dt@kernel.org,
Oleksii_Moisieiev@epam.com, linus.walleij@linaro.org,
gregkh@linuxfoundation.org
Cc: linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, loic.pallardy@st.com,
devicetree@vger.kernel.org, mark.rutland@arm.com, arnd@arndb.de
Subject: Re: [RFC PATCH 1/7] dt-bindings: Document common device controller bindings
Date: Thu, 22 Dec 2022 14:51:00 +0100 [thread overview]
Message-ID: <3072bc2f-6d99-8e52-ee4c-82d5bd46fa5a@kernel.org> (raw)
In-Reply-To: <6e14aecb-e6f5-ec10-a5c5-af6fd1b54e89@foss.st.com>
On 22/12/2022 14:01, Gatien CHEVALLIER wrote:
>
>>
>> Anyway you duplicate work here:
>> https://lore.kernel.org/all/c869d2751125181a55bc8a88c96e3a892b42f37a.1668070216.git.oleksii_moisieiev@epam.com/
>> and maybe you duplicate comments.
>>
>> I don't think there is point to review things twice, so NAK.
> This is a result of me not knowing how to handle this particular case.
> It is a patch that I need to have in my patch set in order to pass Rob's
> bindings check. Otherwise, feature domains bindings defined here will
> not be known in the STM32 System Bus binding file, where they are used.
>
> I wanted to illustrate the use of Oleksii's binding with a practical
> use-case that we want to implement.
Mention patch dependency in the path changelog (---) and that's it. No
tests will be done. You are expected to run tests anyway on your side,
before sending.
>
> What would be the correct way of managing this dependency?
> -Specify something like "On top of ...." in the cover letter/patch and
> reference the other thread?
> -Use a "Depends-On" tag on the YAML binding commit?
> -Something else?
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-12-22 14:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 17:30 [RFC PATCH 0/7] Introduce STM32 system bus Gatien Chevallier
2022-12-21 17:30 ` [RFC PATCH 1/7] dt-bindings: Document common device controller bindings Gatien Chevallier
2022-12-22 10:22 ` Krzysztof Kozlowski
2022-12-22 13:01 ` Gatien CHEVALLIER
2022-12-22 13:51 ` Krzysztof Kozlowski [this message]
2022-12-21 17:30 ` [RFC PATCH 2/7] dt-bindings: bus: add STM32 System Bus Gatien Chevallier
2022-12-21 20:09 ` Rob Herring
2022-12-22 10:24 ` Krzysztof Kozlowski
2022-12-22 13:39 ` Gatien CHEVALLIER
2022-12-22 13:55 ` Krzysztof Kozlowski
2022-12-21 17:30 ` [RFC PATCH 3/7] dt-bindings: bus: add STM32MP15 ETZPC firewall bus bindings Gatien Chevallier
2022-12-22 10:26 ` Krzysztof Kozlowski
2022-12-22 13:51 ` Gatien CHEVALLIER
2022-12-22 13:57 ` Krzysztof Kozlowski
2023-01-04 13:43 ` Gatien CHEVALLIER
2023-01-05 21:53 ` Krzysztof Kozlowski
2023-01-09 11:54 ` Gatien CHEVALLIER
2023-01-11 12:32 ` Krzysztof Kozlowski
2023-01-16 14:06 ` Gatien CHEVALLIER
2022-12-21 17:30 ` [RFC PATCH 4/7] dt-bindings: bus: add STM32MP13 " Gatien Chevallier
2022-12-22 10:26 ` Krzysztof Kozlowski
2022-12-22 13:53 ` Gatien CHEVALLIER
2022-12-21 17:30 ` [RFC PATCH 5/7] bus: stm32_sys_bus: add support for STM32MP15 and STM32MP13 system bus Gatien Chevallier
2022-12-22 10:28 ` Krzysztof Kozlowski
2022-12-22 14:30 ` Gatien CHEVALLIER
2022-12-22 15:19 ` Krzysztof Kozlowski
2022-12-21 17:30 ` [RFC PATCH 6/7] ARM: dts: stm32: add ETZPC as a system bus for STM32MP15x boards Gatien Chevallier
2022-12-22 10:30 ` Krzysztof Kozlowski
2022-12-22 14:42 ` Gatien CHEVALLIER
2022-12-22 15:21 ` Krzysztof Kozlowski
2022-12-22 15:57 ` Gatien CHEVALLIER
2022-12-22 16:00 ` Krzysztof Kozlowski
2022-12-21 17:30 ` [RFC PATCH 7/7] ARM: dts: stm32: add ETZPC as a system bus for STM32MP13x boards Gatien Chevallier
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=3072bc2f-6d99-8e52-ee4c-82d5bd46fa5a@kernel.org \
--to=krzk@kernel.org \
--cc=Oleksii_Moisieiev@epam.com \
--cc=alexandre.torgue@foss.st.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gatien.chevallier@foss.st.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=loic.pallardy@st.com \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).