From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
Conor Dooley <conor.dooley@microchip.com>,
soc@kernel.org
Cc: conor@kernel.org, corbet@lwn.net, devicetree@vger.kernel.org,
krzysztof.kozlowski+dt@linaro.org,
linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
olof@lixom.net, palmer@dabbelt.com, robh+dt@kernel.org,
arnd@arndb.de
Subject: Re: [PATCH v2] Documentation/process: add soc maintainer handbook
Date: Wed, 31 May 2023 08:51:25 +0200 [thread overview]
Message-ID: <ed4c3564-4083-5568-f999-cfd7f02544a7@linaro.org> (raw)
In-Reply-To: <ZHbpb98Yn7SDZ4XZ@debian.me>
On 31/05/2023 08:30, Bagas Sanjaya wrote:
>> +appropriate time later. Most importantly, any incompatible changes should be
>> +clearly pointed out in the patch description and pull request, along with the
>> +expected impact on existing users, such as bootloaders or other operating
>> +systems.
>> +
>> +Driver Branch Dependencies
>> +~~~~~~~~~~~~~~~~~~~~~~~~~~
>> +
>> +A common problem is synchronizing changes between device drivers and devicetree
>> +files, even if a change is compatible in both directions, this may require
>> +coordinating how the changes get merged through different maintainer trees.
>> +
>> +Usually the branch that includes a driver change will also include the
>> +corresponding change to the devicetree binding description, to ensure they are
>> +in fact compatible. This means that the devicetree branch can end up causing
>> +warnings in the "make dtbs_check" step. If a devicetree change depends on
>> +missing additions to a header file in include/dt-bindings/, it will fail the
>> +"make dtbs" step and not get merged.
>
> Sounds like passing `make dtbs` is a merging requirement.
And why shouldn't be?
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-05-31 6:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 12:49 [PATCH v2] Documentation/process: add soc maintainer handbook Conor Dooley
2023-05-30 13:02 ` Jonathan Corbet
2023-05-30 13:12 ` Conor Dooley
2023-05-30 13:14 ` Krzysztof Kozlowski
2023-05-30 15:28 ` Randy Dunlap
2023-05-31 6:30 ` Bagas Sanjaya
2023-05-31 6:51 ` Krzysztof Kozlowski [this message]
2023-05-31 12:22 ` Bagas Sanjaya
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=ed4c3564-4083-5568-f999-cfd7f02544a7@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=arnd@arndb.de \
--cc=bagasdotme@gmail.com \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=olof@lixom.net \
--cc=palmer@dabbelt.com \
--cc=robh+dt@kernel.org \
--cc=soc@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).