Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1507157 > unrolled thread

[PATCH] MAINTAINERS: add more people to the MTD maintainer team

Back to article view | Back to linux.kernel

Contents

  [PATCH] MAINTAINERS: add more people to the MTD maintainer team Boris Brezillon <boris.brezillon@free-electrons.com> - 2016-10-24 14:40 +0200
    Re: [PATCH] MAINTAINERS: add more people to the MTD maintainer team Cyrille Pitchen <cyrille.pitchen@atmel.com> - 2016-10-24 15:10 +0200
      Re: [PATCH] MAINTAINERS: add more people to the MTD maintainer team Marek Vasut <marek.vasut@gmail.com> - 2016-10-24 15:20 +0200
    Re: [PATCH] MAINTAINERS: add more people to the MTD maintainer team Richard Weinberger <richard@nod.at> - 2016-10-24 16:40 +0200

#1507157 — [PATCH] MAINTAINERS: add more people to the MTD maintainer team

Brian has been maintaining the MTD subsystem alone for several years
now, and maintaining such a subsystem can really be time consuming.

Create a maintainer team formed of the most active MTD contributors
to help Brian with this task, which will hopefully improve the
subsystem reactivity.

Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
---
Hi all,

I'm just trying to summarize what I understood the process would be,
don't hesitate to correct me if I'm wrong.

For each release we will assign a specific MTD maintainer which will be
responsible for taking MTD core patches and pulling spi-nor and nand PRs
into the MTD tree and eventually send one or several PRs to Linus.

For fixes that are submitted after -rc1, I usually ask Brian to apply
them directly into the MTD tree (I don't think there's a real need to
prepare spi-nor and nand PRs for fixes), so we can proceed the same
way: ask the maintainer assigned to this release to also take care of
applying fixes and sending PRs to Linus before each -rc.

If you have other ideas, or would like to proceed differently, don't
hesitate propose them.

Thanks,

Boris
---
 MAINTAINERS | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 1cd38a7e0064..cbf9583fdbe7 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7912,6 +7912,10 @@ F:	mm/
 MEMORY TECHNOLOGY DEVICES (MTD)
 M:	David Woodhouse <dwmw2@infradead.org>
 M:	Brian Norris <computersforpeace@gmail.com>
+M:	Boris Brezillon <boris.brezillon@free-electrons.com>
+M:	Marek Vasut <marek.vasut@gmail.com>
+M:	Richard Weinberger <richard@nod.at>
+M:	Cyrille Pitchen <cyrille.pitchen@atmel.com>
 L:	linux-mtd@lists.infradead.org
 W:	http://www.linux-mtd.infradead.org/
 Q:	http://patchwork.ozlabs.org/project/linux-mtd/list/
-- 
2.7.4

[toc] | [next] | [standalone]

#1507179

Hi Boris,

Le 24/10/2016 à 14:35, Boris Brezillon a écrit :
> Brian has been maintaining the MTD subsystem alone for several years
> now, and maintaining such a subsystem can really be time consuming.
> 
> Create a maintainer team formed of the most active MTD contributors
> to help Brian with this task, which will hopefully improve the
> subsystem reactivity.
> 
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Acked-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>

thanks! :)

Cyrille
> ---
> Hi all,
> 
> I'm just trying to summarize what I understood the process would be,
> don't hesitate to correct me if I'm wrong.
> 
> For each release we will assign a specific MTD maintainer which will be
> responsible for taking MTD core patches and pulling spi-nor and nand PRs
> into the MTD tree and eventually send one or several PRs to Linus.
> 
> For fixes that are submitted after -rc1, I usually ask Brian to apply
> them directly into the MTD tree (I don't think there's a real need to
> prepare spi-nor and nand PRs for fixes), so we can proceed the same
> way: ask the maintainer assigned to this release to also take care of
> applying fixes and sending PRs to Linus before each -rc.
> 
> If you have other ideas, or would like to proceed differently, don't
> hesitate propose them.
> 
> Thanks,
> 
> Boris
> ---
>  MAINTAINERS | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 1cd38a7e0064..cbf9583fdbe7 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7912,6 +7912,10 @@ F:	mm/
>  MEMORY TECHNOLOGY DEVICES (MTD)
>  M:	David Woodhouse <dwmw2@infradead.org>
>  M:	Brian Norris <computersforpeace@gmail.com>
> +M:	Boris Brezillon <boris.brezillon@free-electrons.com>
> +M:	Marek Vasut <marek.vasut@gmail.com>
> +M:	Richard Weinberger <richard@nod.at>
> +M:	Cyrille Pitchen <cyrille.pitchen@atmel.com>
>  L:	linux-mtd@lists.infradead.org
>  W:	http://www.linux-mtd.infradead.org/
>  Q:	http://patchwork.ozlabs.org/project/linux-mtd/list/
> 

[toc] | [prev] | [next] | [standalone]

#1507187

On 10/24/2016 03:06 PM, Cyrille Pitchen wrote:
> Hi Boris,
> 
> Le 24/10/2016 à 14:35, Boris Brezillon a écrit :
>> Brian has been maintaining the MTD subsystem alone for several years
>> now, and maintaining such a subsystem can really be time consuming.
>>
>> Create a maintainer team formed of the most active MTD contributors
>> to help Brian with this task, which will hopefully improve the
>> subsystem reactivity.
>>
>> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> Acked-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>
> 
> thanks! :)

Acked-by: Marek Vasut <marek.vasut@gmail.com>

Thanks

-- 
Best regards,
Marek Vasut

[toc] | [prev] | [next] | [standalone]

#1507247

Boris,

On 24.10.2016 14:35, Boris Brezillon wrote:
> Brian has been maintaining the MTD subsystem alone for several years
> now, and maintaining such a subsystem can really be time consuming.
> 
> Create a maintainer team formed of the most active MTD contributors
> to help Brian with this task, which will hopefully improve the
> subsystem reactivity.
> 
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> ---
> Hi all,
> 
> I'm just trying to summarize what I understood the process would be,
> don't hesitate to correct me if I'm wrong.
> 
> For each release we will assign a specific MTD maintainer which will be
> responsible for taking MTD core patches and pulling spi-nor and nand PRs
> into the MTD tree and eventually send one or several PRs to Linus.
> 
> For fixes that are submitted after -rc1, I usually ask Brian to apply
> them directly into the MTD tree (I don't think there's a real need to
> prepare spi-nor and nand PRs for fixes), so we can proceed the same
> way: ask the maintainer assigned to this release to also take care of
> applying fixes and sending PRs to Linus before each -rc.
> 
> If you have other ideas, or would like to proceed differently, don't
> hesitate propose them.

Sounds good to me.
Acked-by: Richard Weinberger <richard@nod.at>

Thanks,
//richard

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web