From: Janusz Krzysztofik <jmkrzyszt@gmail.com>
To: linux-omap@vger.kernel.org, Tony Lindgren <tony@atomide.com>
Cc: linux-arm-kernel@lists.infradead.org,
Aaro Koskinen <aaro.koskinen@iki.fi>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] MAINTAINERS: omap1: Add Janusz as an additional maintainer
Date: Thu, 14 Apr 2022 23:10:37 +0200 [thread overview]
Message-ID: <1681695.QkHrqEjB74@dell> (raw)
In-Reply-To: <20220413081656.27848-1-tony@atomide.com>
On Wednesday, 13 April 2022 10:16:56 CEST Tony Lindgren wrote:
> Janusz has been active with improving and testing the omap1 SoC support
> and has been recently working on adding support for the common clock
> framework.
>
> Cc: Aaro Koskinen <aaro.koskinen@iki.fi>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Janusz Krzysztofik <jmkrzyszt@gmail.com>
> Signed-off-by: Tony Lindgren <tony@atomide.com>
>
> ---
>
> Janusz, does this sound OK to you? :)
Tony, Aaro, thanks for your confidence in me.
Acked-by: Janusz Krzysztofik <jmkrzyszt@gmail.com>
Janusz
>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14389,6 +14389,7 @@ F: arch/arm/boot/dts/am335x-nano.dts
>
> OMAP1 SUPPORT
> M: Aaro Koskinen <aaro.koskinen@iki.fi>
> +M: Janusz Krzysztofik <jmkrzyszt@gmail.com>
> M: Tony Lindgren <tony@atomide.com>
> L: linux-omap@vger.kernel.org
> S: Maintained
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-04-14 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-13 8:16 [PATCH] MAINTAINERS: omap1: Add Janusz as an additional maintainer Tony Lindgren
2022-04-14 21:10 ` Janusz Krzysztofik [this message]
2022-04-20 17:13 ` Aaro Koskinen
2022-04-21 12:35 ` Arnd Bergmann
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=1681695.QkHrqEjB74@dell \
--to=jmkrzyszt@gmail.com \
--cc=aaro.koskinen@iki.fi \
--cc=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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