| Message ID | 20171218154934.6674-1-boris.brezillon@free-electrons.com |
|---|---|
| State | Accepted |
| Delegated to: | Boris Brezillon |
| Headers | show |
| Series | MAINTAINERS: Move all MTD related branches to a single repo | expand |
On Mon, 2017-12-18 at 16:49 +0100, Boris Brezillon wrote: > > 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). You could make a symlink which would mean you don't have to (and mustn't) do that...
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
On Mon, 18 Dec 2017 15:55:35 +0000 David Woodhouse <dwmw2@infradead.org> wrote: > On Mon, 2017-12-18 at 16:49 +0100, Boris Brezillon wrote: > > > > 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). > > You could make a symlink which would mean you don't have to (and > mustn't) do that... Hm, during the transition we still have 2 master branches which are both pulled by Stephen in linux-next, so if we do that before Stephen has updated his script, mtd/next won't appear in linux-next anymore.
Hi Boris, On Mon, 18 Dec 2017 16:49:34 +0100 Boris Brezillon <boris.brezillon@free-electrons.com> wrote: > > 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 Done. This is the l2-mtd tree. > 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 Done. This is the nand tree. I noticed that it has lost its four top commits. > 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 Done. This is the spi-nor tree.
On Mon, 2017-12-18 at 17:00 +0100, Boris Brezillon wrote: > On Mon, 18 Dec 2017 15:55:35 +0000 > David Woodhouse <dwmw2@infradead.org> wrote: > > > On Mon, 2017-12-18 at 16:49 +0100, Boris Brezillon wrote: > > > > > > 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). > > > > You could make a symlink which would mean you don't have to (and > > mustn't) do that... > > Hm, during the transition we still have 2 master branches which are > both pulled by Stephen in linux-next, so if we do that before Stephen > has updated his script, mtd/next won't appear in linux-next anymore. I meant symlinking the individual branch(es), not the whole top-level repo.
On Tue, 19 Dec 2017 07:59:52 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote: > Hi Boris, > > On Mon, 18 Dec 2017 16:49:34 +0100 Boris Brezillon <boris.brezillon@free-electrons.com> wrote: > > > > 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 > > Done. This is the l2-mtd tree. > > > 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 > > Done. This is the nand tree. I noticed that it has lost its four top commits. It should be fixed now. Just forgot to update the nand/next branch on linux-mtd :-/. > > > 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 > > Done. This is the spi-nor tree. > Thanks for updating your script so quickly. Boris
Le 18/12/2017 à 16:49, Boris Brezillon a écrit : > 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> Acked-by: Cyrille Pitchen <cyrille.pitchen@wedev4u.fr> > --- > 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 >
On Mon, 18 Dec 2017 16:49:34 +0100 Boris Brezillon <boris.brezillon@free-electrons.com> wrote: > 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). Applied to mtd/next (on the linux-mtd repo). I also created symlinks for l2-mtd/master, l2-mtd/nand/next and l2-mtd/spi-nor/next as suggested by David. So please stop pushing things on l2-mtd. Thanks, Boris > > 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
On Mon, Dec 18, 2017 at 04:49:34PM +0100, Boris Brezillon wrote: > 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 Eh, I'm not sure I qualify as "active" these days, but anyway... > 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). Seems fine. Acked-by: Brian Norris <computersforpeace@gmail.com> (Oh, well you've already pushed it.)
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
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(-)