Re: [PATCH -next v2 5/6] dt-bindings: ipmi: aspeed,kcs-bmc: add 'clocks' as a required property
From: Joel Stanley <joel@jms.id.au>
Date: 2021-11-03 22:45:53
Also in:
linux-arm-kernel, linux-aspeed
From: Joel Stanley <joel@jms.id.au>
Date: 2021-11-03 22:45:53
Also in:
linux-arm-kernel, linux-aspeed
On Wed, 3 Nov 2021 at 17:27, Jae Hyun Yoo [off-list ref] wrote:
On 11/3/2021 9:29 AM, Rob Herring wrote:
quoted
It's possible that 'clocks' was always required or that it never worked without clocks, then this change is okay. Looking at this patch, I have no way to know that. The commit message has to explain that. A commit message needs to answer WHY are you making the change. You don't really need WHAT the change is as anyone can read the diff.Then what would be better? Would it be good enough if I add more detail commit message including a note that dtb recompiling is required? Or, should I change this series to treat the 'clocks' as an optional property? Can you please share your thought?
Make it essential. It was only by accident that things have worked without this change. While keeping backwards compatibility with dtbs is a goal we strive for, in practice we use the dtb from the corresponding kernel source tree, so as long as the patch to the driver is applied in the same place as the patch to the device tree no systems will break.