From: Thierry Reding <thierry.reding@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: linux-i2c@vger.kernel.org, Thierry Reding <treding@nvidia.com>,
Peter Rosin <peda@lysator.liu.se>,
Andi Shyti <andi.shyti@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: i2c: i2c-mux-pinctrl: change maintainer
Date: Mon, 15 Jun 2026 20:38:24 +0200 [thread overview]
Message-ID: <ajBGibftf679T6P4@arch.a226c7d-lcedt> (raw)
In-Reply-To: <20260611122704.7559-2-wsa+renesas@sang-engineering.com>
[-- Attachment #1: Type: text/plain, Size: 1571 bytes --]
On Thu, Jun 11, 2026 at 02:26:24PM +0200, Wolfram Sang wrote:
> The YAML conversion added me as maintainer but I can't recall being
> asked nor do I want to maintain it. Thierry has created the YAML file
> and works for the company which contributed the driver.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>
> @Thierry: are you okay with this change?
>
> Documentation/devicetree/bindings/i2c/i2c-mux-pinctrl.yaml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/i2c/i2c-mux-pinctrl.yaml b/Documentation/devicetree/bindings/i2c/i2c-mux-pinctrl.yaml
> index 2e3d555eb96c..f7502da71909 100644
> --- a/Documentation/devicetree/bindings/i2c/i2c-mux-pinctrl.yaml
> +++ b/Documentation/devicetree/bindings/i2c/i2c-mux-pinctrl.yaml
> @@ -7,7 +7,7 @@ $schema: http://devicetree.org/meta-schemas/core.yaml#
> title: Pinctrl-based I2C Bus Mux
>
> maintainers:
> - - Wolfram Sang <wsa@kernel.org>
> + - Thierry Reding <treding@nvidia.com>
>
> description: |
> This binding describes an I2C bus multiplexer that uses pin multiplexing to route the I2C
By default I used to list the subsystem maintainer as the bindings
maintainer if the binding wasn't Tegra-specific, or in this case the
original author wasn't active anymore.
I'm fine being listed as the maintainer for this if you don't want to,
but I prefer to use the thierry.reding@kernel.org email address for
communication.
With that:
Acked-by: Thierry Reding <treding@nvidia.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-06-15 18:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-11 12:26 [PATCH] dt-bindings: i2c: i2c-mux-pinctrl: change maintainer Wolfram Sang
2026-06-11 17:18 ` Conor Dooley
2026-06-15 18:38 ` Thierry Reding [this message]
2026-06-15 21:15 ` Andi Shyti
2026-06-16 11:09 ` Thierry Reding
2026-06-16 6:04 ` Wolfram Sang
2026-06-16 11:15 ` Thierry Reding
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=ajBGibftf679T6P4@arch.a226c7d-lcedt \
--to=thierry.reding@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=peda@lysator.liu.se \
--cc=robh@kernel.org \
--cc=treding@nvidia.com \
--cc=wsa+renesas@sang-engineering.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