From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Biju Das <biju.das.jz@bp.renesas.com>, Lee Jones <lee@kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Support Opensource <support.opensource@diasemi.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Zhang Rui <rui.zhang@intel.com>,
Lukasz Luba <lukasz.luba@arm.com>,
Steve Twiss <stwiss.opensource@diasemi.com>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
"biju.das.au" <biju.das.au@gmail.com>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH v3.1 0/8] Convert DA906{1,2} bindings to json-schema
Date: Wed, 6 Dec 2023 12:18:00 +0100 [thread overview]
Message-ID: <33b097c7-0c7f-457c-b597-19c504df5a36@linaro.org> (raw)
In-Reply-To: <TYVPR01MB112796A859B42CC4AC6F6EC838684A@TYVPR01MB11279.jpnprd01.prod.outlook.com>
On 06/12/2023 12:16, Biju Das wrote:
> Hi Krzysztof Kozlowski,
>
> Thanks for the feedback.
>
>> -----Original Message-----
>> From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> Sent: Wednesday, December 6, 2023 11:06 AM
>> Subject: Re: [PATCH v3.1 0/8] Convert DA906{1,2} bindings to json-schema
>>
>> On 04/12/2023 18:25, Biju Das wrote:
>>> Convert the below bindings to json-schema
>>> 1) DA906{1,2} mfd bindings
>>> 2) DA906{1,2,3} onkey bindings
>>> 3) DA906{1,2,3} thermal bindings
>>>
>>> Also add fallback for DA9061 watchdog device and document
>>> DA9063 watchdog device.
>>>
>>> v3->v3.1:
>>> * Patch#1 is merge of patch#1 from v2 + patch#8 from v2.
>>> * Dropped comment for d9061 watchdog fallback
>>> * Replaced enum->const for dlg,da9061-watchdog and its fallback.
>>> * Restored patch#4 in series 1 and dropped the thermal example
>>> * Added Ack from Conor Dooley for da9063 watchdog binding support.
>>> * Updated title DA9062/61->DA906{1,2,3} as it supports DA9063.
>>> * Retained Rb tag since the changes are trivial.
>>> * Added Ack from Conor for updating watchdog property
>>> * Dropped link to product information.
>>> * Patch#5(onkey) is squashed with patch#6 and patch#9 from v2.
>>> * Replaced enum->const for dlg,da9061-onkey and its fallback.
>>> * Dropped example
>>> * Restored the thermal binding patch from v2.
>>> * Dropped example
>>> * Replaced enum->const for compatible property.
>>> * Added Rb tag from Rob and retained Rb tag as changes are trivial.
>>> * Added Ack from Conor Dooley for patch#7.
>>> * Split the thermal binding patch separate
>>> * Updated the description
>>
>>
>> Hundreds of changes and just "3 -> 3.1"? This does not make sense.
>
> Bot reported some issues with v2. So immediately I send v3 which clashed
> with review comments from Conor and Rob.
>
> No one has reviewed V3.
>
> V3.1 = basically Review comments from v2 + Fix for Bot errors.
v4, don't introduce some minor numbering to create impression of no
changes, especially if you have multiple changes.
>
>
>>
>> Also, use normal versioning:
>>
>> b4 diff '<20231204172510.35041-9-biju.das.jz@bp.renesas.com>'
>> Grabbing thread from
>> lore.kernel.org/all/20231204172510.35041-9-
>> biju.das.jz@bp.renesas.com/t.mbox.gz
>> ---
>> Analyzing 21 messages in the thread
>> ERROR: Could not auto-find previous revision
>> Run "b4 am -T" manually, then "b4 diff -m mbx1 mbx2"
>
>
> Can you please clarify more? I may be missing something here?
>
> I just rebase to linux-next and send patches using the command
>
> git send-email --dry-run --annotate *.patch
>
> All patches Updated with TO and CC recipients.
>
> Am I missing anything here w.r.to versioning?
v3 -> v4.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-12-06 11:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-04 17:25 [PATCH v3.1 0/8] Convert DA906{1,2} bindings to json-schema Biju Das
2023-12-04 17:25 ` [PATCH v3.1 5/8] dt-bindings: input: Convert da906{1,2,3} onkey " Biju Das
2023-12-05 17:01 ` Conor Dooley
2023-12-04 17:25 ` [PATCH v3.1 8/8] dt-bindings: mfd: dlg,da9063: Convert da9062 " Biju Das
2023-12-05 17:12 ` Conor Dooley
2023-12-05 18:52 ` Biju Das
2023-12-06 11:06 ` [PATCH v3.1 0/8] Convert DA906{1,2} bindings " Krzysztof Kozlowski
2023-12-06 11:16 ` Biju Das
2023-12-06 11:18 ` Krzysztof Kozlowski [this message]
2023-12-06 11:26 ` Biju Das
2023-12-06 13:58 ` Rob Herring
2023-12-06 15:14 ` Biju Das
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=33b097c7-0c7f-457c-b597-19c504df5a36@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=stwiss.opensource@diasemi.com \
--cc=support.opensource@diasemi.com \
/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).