[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250819192455.3d294562@jic23-huawei>
Date: Tue, 19 Aug 2025 19:24:55 +0100
From: Jonathan Cameron <jic23@...nel.org>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Ben Collins <bcollins@...nel.org>, linux-iio@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, Ben Collins
<bcollins@...ter.com>, David Lechner <dlechner@...libre.com>, Nuno Sa
<nuno.sa@...log.com>, Andy Shevchenko <andy@...nel.org>, Rob Herring
<robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Andrew Hepp <andrew.hepp@...pp.dev>
Subject: Re: [PATCH v5 0/5] iio: mcp9600: Features and improvements
On Tue, 19 Aug 2025 08:55:44 +0200
Krzysztof Kozlowski <krzk@...nel.org> wrote:
> On Mon, Aug 18, 2025 at 02:32:08PM -0400, Ben Collins wrote:
> > From: Ben Collins <bcollins@...ter.com>
> >
> > ChangeLog:
> > v5 -> v6:
> > - Fix accidental typo added in dt-bindings: IRQ_TYPE_EDGE_RISIN
> > - Correct some constraints in dt-bindings
> > - Reverse if/then for mcp9601 vs mcp9600 constraints in dt-bindings
> > - Updates to changelog for patch 2/6 (dt-bindings mcp9600)
> > - Cleanup tabs that were converted to spaces
> > - Split thermocouple-type default to separate patch
>
> Please start using b4, so you will get changelogs with lore links for
> free and ALL your patches will be properly versioned. git can do that
> as well - git format-patch -v5 --cover-letter, if you don't want to use
> b4.
Second that. This is what it looks like in patchwork that I use
for managing reviews / merges etc.
https://patchwork.kernel.org/project/linux-iio/list/?series=992678
version number not easy to find as it gets dropped from the series title
and is only normally listed for the patches.
>
> Best regards,
> Krzysztof
>
Powered by blists - more mailing lists