[PATCH 0/4] Why no v2?

Daniel Matyas posted 4 patches 2 years, 3 months ago
.../bindings/hwmon/adi,max31827.yaml          |  35 ++
Documentation/hwmon/max31827.rst              |  73 +++-
drivers/hwmon/max31827.c                      | 397 +++++++++++++-----
3 files changed, 395 insertions(+), 110 deletions(-)
[PATCH 0/4] Why no v2?
Posted by Daniel Matyas 2 years, 3 months ago
This is kind of v2, but not exactly. Major changes were applied and
commits were separated. The latter is the main reason why I did not call
this v2.

Briefly, this is what changed compared to the previoius patch:
 - separate commit for: cleanup, dts doc, new dts props in driver,
   resolution attribute
 - timeout can be enabled now from the devicetree; no timeout attribute
 - support for max31828 and max31829

Daniel Matyas (4):
  hwmon: max31827: Make code cleaner
  dt-bindings: hwmon: Added new properties to the devicetree
  hwmon: max31827: Handle new properties from the devicetree
  hwmon: max31827: Add custom attribute for resolution

 .../bindings/hwmon/adi,max31827.yaml          |  35 ++
 Documentation/hwmon/max31827.rst              |  73 +++-
 drivers/hwmon/max31827.c                      | 397 +++++++++++++-----
 3 files changed, 395 insertions(+), 110 deletions(-)

-- 
2.34.1
Re: [PATCH 0/4] Why no v2?
Posted by Guenter Roeck 2 years, 3 months ago
On 9/13/23 08:21, Daniel Matyas wrote:
> This is kind of v2, but not exactly. Major changes were applied and
> commits were separated. The latter is the main reason why I did not call
> this v2.
> 

That is neither a reason nor a valid argument. Just call it v2 and mark
the added patch(es) with a changelog along the line of "v2: Added patch".

And a subject of "Why no v2?" is really useless and pointless.

Guenter