All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Thierry Reding <thierry.reding@kernel.org>
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: Tue, 16 Jun 2026 08:04:29 +0200	[thread overview]
Message-ID: <ajDnbQJhfeICowkn@shikoro> (raw)
In-Reply-To: <ajBGibftf679T6P4@arch.a226c7d-lcedt>

[-- Attachment #1: Type: text/plain, Size: 834 bytes --]

Hi Thierry,

> 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 understand that. Yet, since I handed I2C over to Andi now, this entry
becomes kind of stale then. I wanted to drop the maintainers:-property
completely to avoid changing all the maintainers entry once a subsystem
gets handed over, but Rob disagreed to that.

> 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.

Ok, thank you, will fix.

> With that:
> 
> Acked-by: Thierry Reding <treding@nvidia.com>

I will use your kernel.org address for the ack then as well, I guess.

Happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2026-06-16  6:04 UTC|newest]

Thread overview: 5+ 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
2026-06-15 21:15   ` Andi Shyti
2026-06-16  6:04   ` Wolfram Sang [this message]

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=ajDnbQJhfeICowkn@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --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=thierry.reding@kernel.org \
    --cc=treding@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.