Devicetree
 help / color / mirror / Atom feed
From: Marek Vasut <marex@nabladev.com>
To: Bartosz Golaszewski <brgl@kernel.org>
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Conor Dooley <conor+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Linus Walleij <linusw@kernel.org>, Rob Herring <robh@kernel.org>,
	devicetree@vger.kernel.org, kernel@dh-electronics.com,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 02/10] dt-bindings: gpio: pca95xx: Document Kinetic KTS1622
Date: Mon, 13 Jul 2026 12:33:02 +0200	[thread overview]
Message-ID: <47178bf9-1fc7-4585-aa17-37ec07152b01@nabladev.com> (raw)
In-Reply-To: <CAMRc=Mds7FAg=e-JGWxK=9vn5A0sdYDhpZ7Wvo3eCKV1tyNpKw@mail.gmail.com>

On 7/13/26 10:36 AM, Bartosz Golaszewski wrote:
> On Sat, 11 Jul 2026 22:59:31 +0200, Marek Vasut <marex@nabladev.com> said:
>> The Kinetic Technologies KTS1622 is a 16-bit general-purpose I/O
>> expander via the I2C bus for microcontrollers when additional I/Os
>> are needed while keeping interconnections to the minimum. Datasheet
>> comparison suggests that it is compatible with TCAL6416, add the
>> compatible string and TCAL6416 as a fallback compatible.
>>
>> Signed-off-by: Marek Vasut <marex@nabladev.com>
>> ---
>> Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
>> Cc: Bartosz Golaszewski <brgl@kernel.org>
>> Cc: Conor Dooley <conor+dt@kernel.org>
>> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
>> Cc: Linus Walleij <linusw@kernel.org>
>> Cc: Rob Herring <robh@kernel.org>
>> Cc: devicetree@vger.kernel.org
>> Cc: kernel@dh-electronics.com
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: linux-gpio@vger.kernel.org
>> Cc: linux-kernel@vger.kernel.org
>> Cc: linux-stm32@st-md-mailman.stormreply.com
>> ---
>>   Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml b/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml
>> index 4f955f855e1ab..4631388a7d914 100644
>> --- a/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml
>> +++ b/Documentation/devicetree/bindings/gpio/gpio-pca95xx.yaml
>> @@ -22,6 +22,9 @@ properties:
>>         - items:
>>             - const: diodes,pi4ioe5v6534q
>>             - const: nxp,pcal6534
>> +      - items:
>> +          - const: kinetic,kts1622
>> +          - const: ti,tcal6416
>>         - items:
>>             - enum:
>>                 - exar,xra1202
>> --
>> 2.53.0
>>
>>
> 
> I applied this. I would have sent a b4 notification but got this instead:
> 
> $ b4 ty -all
> Auto-thankanating commits in gpio/for-next
> Found 9 of your commits since 1.week
> Calculating patch hashes, may take a moment...
>    Located: [PATCH 00/10] arm64: dts: st: Add support for DH
> electronics STM32MP23xx/STM32MP25xx DHCOS SoM and Breakout Board and
> DHSBC
> ---
> Generating 1 thank-you letters
>    Writing: ./marex_nabladev_com_patch_00_10_arm64_dts_st_add_support_for_dh_electronics_stm32mp23xx_stm32mp25xx_dhcos_som_and_breakout_board_and_dhsbc.thanks
> Traceback (most recent call last):
>    File "/usr/bin/b4", line 8, in <module>
>      sys.exit(cmd())
>               ~~~^^
>    File "/usr/lib/python3/dist-packages/b4/command.py", line 417, in cmd
>      cmdargs.func(cmdargs)
>      ~~~~~~~~~~~~^^^^^^^^^
>    File "/usr/lib/python3/dist-packages/b4/command.py", line 113, in cmd_ty
>      b4.ty.main(cmdargs)
>      ~~~~~~~~~~^^^^^^^^^
>    File "/usr/lib/python3/dist-packages/b4/ty.py", line 681, in main
>      auto_thankanator(cmdargs)
>      ~~~~~~~~~~~~~~~~^^^^^^^^^
>    File "/usr/lib/python3/dist-packages/b4/ty.py", line 386, in auto_thankanator
>      send_messages(applied, wantbranch, cmdargs)
>      ~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>    File "/usr/lib/python3/dist-packages/b4/ty.py", line 452, in send_messages
>      with open(outfile, 'wb') as fh:
>           ~~~~^^^^^^^^^^^^^^^
> OSError: [Errno 36] File name too long:
> './marex_nabladev_com_patch_00_10_arm64_dts_st_add_support_for_dh_electronics_stm32mp23xx_stm32mp25xx_dhcos_som_and_breakout_board_and_dhsbc.thanks'
B4 bug ?

  reply	other threads:[~2026-07-13 23:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11 20:59 [PATCH 00/10] arm64: dts: st: Add support for DH electronics STM32MP23xx/STM32MP25xx DHCOS SoM and Breakout Board and DHSBC Marek Vasut
2026-07-11 20:59 ` [PATCH 01/10] dt-bindings: arm: stm32: Document " Marek Vasut
2026-07-13  7:48   ` Krzysztof Kozlowski
2026-07-13 10:31     ` Marek Vasut
2026-07-11 20:59 ` [PATCH 02/10] dt-bindings: gpio: pca95xx: Document Kinetic KTS1622 Marek Vasut
2026-07-13  7:49   ` Krzysztof Kozlowski
2026-07-13  8:36   ` Bartosz Golaszewski
2026-07-13 10:33     ` Marek Vasut [this message]
2026-07-11 20:59 ` [PATCH 03/10] arm64: dts: st: Fix SDMMC1 indent on stm32mp231 Marek Vasut
2026-07-11 20:59 ` [PATCH 04/10] arm64: dts: st: Fix SDMMC1 indent on stm32mp251 Marek Vasut
2026-07-11 20:59 ` [PATCH 05/10] arm64: dts: st: Add SDMMC2 and SDMMC3 nodes on stm32mp231 Marek Vasut
2026-07-11 20:59 ` [PATCH 06/10] arm64: dts: st: Add SDMMC2 and SDMMC3 nodes on stm32mp251 Marek Vasut
2026-07-11 20:59 ` [PATCH 07/10] arm64: dts: st: Add OMM node on stm32mp231 Marek Vasut
2026-07-11 20:59 ` [PATCH 08/10] arm64: dts: st: Add pinmux nodes for DH electronics STM32MP23xx/STM32MP25xx DHCOS SoM and Breakout Board Marek Vasut
2026-07-11 21:17   ` sashiko-bot
2026-07-11 20:59 ` [PATCH 09/10] arm64: dts: st: Add support for DH electronics STM32MP23xx/STM32MP25xx DHCOS SoM and Breakout Board and DHSBC Marek Vasut
2026-07-11 21:18   ` sashiko-bot
2026-07-11 20:59 ` [PATCH 10/10] MAINTAINERS: Add DH electronics DHCOS SoM entry and fix email address Marek Vasut
2026-07-13  7:51   ` Krzysztof Kozlowski
2026-07-13 13:25     ` Marek Vasut
2026-07-13 13:45       ` Krzysztof Kozlowski

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=47178bf9-1fc7-4585-aa17-37ec07152b01@nabladev.com \
    --to=marex@nabladev.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@dh-electronics.com \
    --cc=krzk+dt@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=robh@kernel.org \
    /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