[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0ece18f0-2160-4cb3-a4a1-d566179f908f@kernel.org>
Date: Mon, 30 Jun 2025 10:18:15 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Alexey Klimov <alexey.klimov@...aro.org>,
Srinivas Kandagatla <srini@...nel.org>, Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Stephen Boyd <sboyd@...nel.org>
Cc: Lee Jones <lee@...nel.org>, Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>, linux-arm-msm@...r.kernel.org,
linux-sound@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>,
Srinivas Kandagatla <srinivas.kandagatla@....qualcomm.com>
Subject: Re: [PATCH 2/3] dt-bindings: mfd: qcom,spmi-pmic: add pm4125 audio
codec
On 28/06/2025 18:42, Alexey Klimov wrote:
> On Thu Jun 26, 2025 at 9:48 AM BST, Krzysztof Kozlowski wrote:
>> On 26/06/2025 01:50, Alexey Klimov wrote:
>>> PM4125 has audio codec hardware block. Add pattern for respecive node
>>> so the devicetree for those blocks can be validated properly.
>>>
>>> Signed-off-by: Alexey Klimov <alexey.klimov@...aro.org>
>>
>> Remember to ALWAYS explain the dependencies between patches (merging
>> strategy), because this now creates impression is independent patch. It
>> is not and should be squashed into previous.
>
> What's the proper way to describe such dependency?
The best changelog. Acceptable is also cover letter, although some
people skip cover letters.
Best regards,
Krzysztof
Powered by blists - more mailing lists