From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Adam Thomson <DLG-Adam.Thomson.Opensource@dm.renesas.com>
Cc: linux-kernel@vger.kernel.org,
DLG Support Opensource <DLG-Support.Opensource@lm.renesas.com>
Subject: Re: [PATCH] MAINTAINERS: Update Dialog Semiconductor mailing list, website
Date: Mon, 1 Aug 2022 13:21:18 +0200 [thread overview]
Message-ID: <Yue3LpR7FdHygLze@kroah.com> (raw)
In-Reply-To: <20220801110140.7DF6280007F@slsrvapps-01.diasemi.com>
On Mon, Aug 01, 2022 at 11:01:40AM +0000, Adam Thomson wrote:
> Now Dialog Semiconductor is part of Renesas, the mailing list and
> web addresses have been updated. This commit aligns with those
> recent changes.
>
> Signed-off-by: Adam Thomson <DLG-Adam.Thomson.Opensource@dm.renesas.com>
> ---
> MAINTAINERS | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 64379c699903..b1015d06d429 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5923,9 +5923,9 @@ F: arch/arm/boot/dts/stm32mp1*-dhcom-*
> F: arch/arm/boot/dts/stm32mp1*-dhcor-*
>
> DIALOG SEMICONDUCTOR DRIVERS
> -M: Support Opensource <support.opensource@diasemi.com>
> +M: DLG Support Opensource <DLG-Support.Opensource@lm.renesas.com>
I strongly discourage any anonymous "group alias" for maintainers of any
kernel code, as that takes away the personal responsibility from the
maintainer entirely, which defeats one of the strongest reasons that
open source development efforts work so well.
Why not just switch this over to you instead?
thanks,
greg k-h
next prev parent reply other threads:[~2022-08-01 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 11:01 [PATCH] MAINTAINERS: Update Dialog Semiconductor mailing list, website Adam Thomson
2022-08-01 11:21 ` Greg Kroah-Hartman [this message]
2022-08-01 12:13 ` DLG Adam Thomson
2022-08-01 12:23 ` Greg Kroah-Hartman
2022-08-02 14:48 ` DLG Adam Thomson
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=Yue3LpR7FdHygLze@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=DLG-Adam.Thomson.Opensource@dm.renesas.com \
--cc=DLG-Support.Opensource@lm.renesas.com \
--cc=linux-kernel@vger.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