From: Shawn Guo <shawnguo2@yeah.net>
To: Michael Walle <mwalle@kernel.org>
Cc: Rob Herring <robh@kernel.org>, Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: Drop Li Yang as maintainer for all bindings
Date: Sun, 16 Jun 2024 20:26:59 +0800 [thread overview]
Message-ID: <Zm7aE5+1KONVCi1i@dragon> (raw)
In-Reply-To: <20240604142249.1957762-1-mwalle@kernel.org>
On Tue, Jun 04, 2024 at 04:22:48PM +0200, Michael Walle wrote:
> Remove Li Yang from all device tree bindings because mails to this
> address are bouncing.
>
> Commit fbdd90334a62 ("MAINTAINERS: Drop Li Yang as their email address
> stopped working") already removed the entry from the MAINTAINERS but
> didn't address all the in-file entries of the device tree bindings.
>
> Signed-off-by: Michael Walle <mwalle@kernel.org>
Applied both, thanks!
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo2@yeah.net>
To: Michael Walle <mwalle@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: Drop Li Yang as maintainer for all bindings
Date: Sun, 16 Jun 2024 20:26:59 +0800 [thread overview]
Message-ID: <Zm7aE5+1KONVCi1i@dragon> (raw)
In-Reply-To: <20240604142249.1957762-1-mwalle@kernel.org>
On Tue, Jun 04, 2024 at 04:22:48PM +0200, Michael Walle wrote:
> Remove Li Yang from all device tree bindings because mails to this
> address are bouncing.
>
> Commit fbdd90334a62 ("MAINTAINERS: Drop Li Yang as their email address
> stopped working") already removed the entry from the MAINTAINERS but
> didn't address all the in-file entries of the device tree bindings.
>
> Signed-off-by: Michael Walle <mwalle@kernel.org>
Applied both, thanks!
next prev parent reply other threads:[~2024-06-17 23:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 14:22 [PATCH 1/2] dt-bindings: Drop Li Yang as maintainer for all bindings Michael Walle
2024-06-04 14:22 ` Michael Walle
2024-06-04 14:22 ` Michael Walle
2024-06-04 14:22 ` [RFC PATCH 2/2] dt-bindings: memory: fsl: replace maintainer Michael Walle
2024-06-04 14:22 ` Michael Walle
2024-06-04 14:22 ` Michael Walle
2024-06-11 8:49 ` Krzysztof Kozlowski
2024-06-11 8:49 ` Krzysztof Kozlowski
2024-06-11 8:49 ` Krzysztof Kozlowski
2024-06-17 3:24 ` Shawn Guo
2024-06-17 3:24 ` Shawn Guo
2024-06-17 6:08 ` Krzysztof Kozlowski
2024-06-17 6:08 ` Krzysztof Kozlowski
2024-06-17 6:08 ` (subset) " Krzysztof Kozlowski
2024-06-17 6:08 ` Krzysztof Kozlowski
2024-06-11 8:48 ` [PATCH 1/2] dt-bindings: Drop Li Yang as maintainer for all bindings Krzysztof Kozlowski
2024-06-11 8:48 ` Krzysztof Kozlowski
2024-06-11 8:48 ` Krzysztof Kozlowski
2024-06-16 12:26 ` Shawn Guo [this message]
2024-06-16 12:26 ` Shawn Guo
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=Zm7aE5+1KONVCi1i@dragon \
--to=shawnguo2@yeah.net \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mwalle@kernel.org \
--cc=robh@kernel.org \
--cc=shawnguo@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 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.