Linux-MIPS Archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Serge Semin <Sergey.Semin@BAIKALELECTRONICS.ru>
Cc: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Serge Semin <fancer.lancer@gmail.com>,
	Alexey Malahov <Alexey.Malahov@BAIKALELECTRONICS.ru>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-mips@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-hwmon@vger.kernel.org, kernel-janitors@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] MAINTAINERS: Add maintainer for MIPS Baikal-T1 platform code
Date: Tue, 20 Feb 2024 14:36:43 +0100	[thread overview]
Message-ID: <ZdSq66XhxrqgyNBy@alpha.franken.de> (raw)
In-Reply-To: <20231122170506.27267-4-Sergey.Semin@baikalelectronics.ru>

On Wed, Nov 22, 2023 at 08:04:52PM +0300, Serge Semin wrote:
> Add myself as a maintainer of the MIPS Baikal-T1 platform-specific
> drivers. The arch-code hasn't been submitted yet, but will be soon enough.
> Until then it's better to have the already available drivers marked as
> maintained.
> 
> Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
> ---
>  MAINTAINERS | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 52ee905c50f4..a56e241608ae 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14491,6 +14491,17 @@ F:	arch/mips/
>  F:	drivers/platform/mips/
>  F:	include/dt-bindings/mips/
>  
> +MIPS BAIKAL-T1 PLATFORM
> +M:	Serge Semin <fancer.lancer@gmail.com>
> +L:	linux-mips@vger.kernel.org
> +S:	Supported
> +F:	Documentation/devicetree/bindings/bus/baikal,bt1-*.yaml
> +F:	Documentation/devicetree/bindings/clock/baikal,bt1-*.yaml
> +F:	drivers/bus/bt1-*.c
> +F:	drivers/clk/baikal-t1/
> +F:	drivers/memory/bt1-l2-ctl.c
> +F:	drivers/mtd/maps/physmap-bt1-rom.[ch]
> +
>  MIPS BOSTON DEVELOPMENT BOARD
>  M:	Paul Burton <paulburton@kernel.org>
>  L:	linux-mips@vger.kernel.org
> -- 
> 2.42.1

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      parent reply	other threads:[~2024-02-20 13:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-22 17:04 [PATCH 0/3] MAINTAINERS: Add MIPS Baikal-T1 SoC bits maintainer Serge Semin
2023-11-22 17:04 ` [PATCH 1/3] MAINTAINERS: Add maintainer for Baikal-T1 PVT hwmon driver Serge Semin
2023-12-11 14:32   ` Guenter Roeck
2023-11-22 17:04 ` [PATCH 2/3] MAINTAINERS: Add maintainer for Baikal-T1 PCIe driver Serge Semin
2023-11-22 17:04 ` [PATCH 3/3] MAINTAINERS: Add maintainer for MIPS Baikal-T1 platform code Serge Semin
2024-02-11 10:24   ` Serge Semin
2024-02-20 13:36   ` Thomas Bogendoerfer [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=ZdSq66XhxrqgyNBy@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=Alexey.Malahov@BAIKALELECTRONICS.ru \
    --cc=Sergey.Semin@BAIKALELECTRONICS.ru \
    --cc=arnd@arndb.de \
    --cc=fancer.lancer@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas.bulwahn@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).