All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	Marek Vasut <marek.vasut@gmail.com>,
	Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] MAINTAINERS: Move all MTD related branches to a single repo
Date: Mon, 18 Dec 2017 16:57:45 +0100	[thread overview]
Message-ID: <1696722.1RW9e4FE9p@blindfold> (raw)
In-Reply-To: <20171218154934.6674-1-boris.brezillon@free-electrons.com>

Boris,

Am Montag, 18. Dezember 2017, 16:49:34 CET schrieb Boris Brezillon:
> Historically branches targeting the next release (and pulled in
> linux-next) have been pushed on the l2-mtd repo and fixes branches on
> the linux-mtd one. Now that all MTD maintainers have RW permissions on
> linux-mtd tree, there's no good reason to have two different trees.
> Move all -next branches to linux-mtd.
> 
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> Cc: Stephen Rothwell <sfr@canb.auug.org.au>
> Cc: Marek Vasut <marek.vasut@gmail.com>
> Cc: Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>
> Cc: Richard Weinberger <richard@nod.at>
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Brian Norris <computersforpeace@gmail.com>
> ---
> Hi MTD maintainers,
> 
> As discussed a few weeks ago, this patch is moving all MTD related
> branches to the linux-mtd repo in an attempt to make things easier
> for maintainers (it's not unusal to push the next or fixes branch to
> the wrong repo) and developers (it's hard to know where the patch was
> applied, especially when the maintainer does not specify it in his
> reply, which I do a lot :)).
> 
> Once I have gathered acks from all active maintainers, I'll apply this
> patch to the mtd/next branch and ask Stephen to pull next branches from
> their new locations.
> 
> In the meantime, we should try to keep both l2-mtd and linux-mtd synced
> (that means pushing the xxx/next branches on both l2-mtd and mtd-next).
> 
> Regards,
> 
> Boris
> ---
>  MAINTAINERS | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index aa71ab52fd76..10732ecfc937 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -8956,7 +8956,7 @@ L:	linux-mtd@lists.infradead.org
>  W:	http://www.linux-mtd.infradead.org/
>  Q:	http://patchwork.ozlabs.org/project/linux-mtd/list/
>  T:	git git://git.infradead.org/linux-mtd.git master
> -T:	git git://git.infradead.org/l2-mtd.git master
> +T:	git git://git.infradead.org/linux-mtd.git mtd/next
>  S:	Maintained
>  F:	Documentation/devicetree/bindings/mtd/
>  F:	drivers/mtd/
> @@ -9344,7 +9344,7 @@ L:	linux-mtd@lists.infradead.org
>  W:	http://www.linux-mtd.infradead.org/
>  Q:	http://patchwork.ozlabs.org/project/linux-mtd/list/
>  T:	git git://git.infradead.org/linux-mtd.git nand/fixes
> -T:	git git://git.infradead.org/l2-mtd.git nand/next
> +T:	git git://git.infradead.org/linux-mtd.git nand/next
>  S:	Maintained
>  F:	drivers/mtd/nand/
>  F:	include/linux/mtd/*nand*.h
> @@ -12761,7 +12761,7 @@ L:	linux-mtd@lists.infradead.org
>  W:	http://www.linux-mtd.infradead.org/
>  Q:	http://patchwork.ozlabs.org/project/linux-mtd/list/
>  T:	git git://git.infradead.org/linux-mtd.git spi-nor/fixes
> -T:	git git://git.infradead.org/l2-mtd.git spi-nor/next
> +T:	git git://git.infradead.org/linux-mtd.git spi-nor/next
>  S:	Maintained
>  F:	drivers/mtd/spi-nor/
>  F:	include/linux/mtd/spi-nor.h

Acked-by: Richard Weinberger <richard@nod.at>

Thanks,
//richard

  parent reply	other threads:[~2017-12-18 15:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-18 15:49 [PATCH] MAINTAINERS: Move all MTD related branches to a single repo Boris Brezillon
2017-12-18 15:55 ` David Woodhouse
2017-12-18 16:00   ` Boris Brezillon
2017-12-18 21:05     ` David Woodhouse
2017-12-18 15:57 ` Richard Weinberger [this message]
2017-12-18 20:59 ` Stephen Rothwell
2017-12-18 21:07   ` Boris Brezillon
2017-12-19 15:34 ` Cyrille Pitchen
2017-12-20 15:26 ` Boris Brezillon
2017-12-20 19:07 ` Brian Norris

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=1696722.1RW9e4FE9p@blindfold \
    --to=richard@nod.at \
    --cc=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=cyrille.pitchen@wedev4u.fr \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marek.vasut@gmail.com \
    --cc=sfr@canb.auug.org.au \
    /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.