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

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

  reply	other threads:[~2017-12-18 21:07 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
2017-12-18 20:59 ` Stephen Rothwell
2017-12-18 21:07   ` Boris Brezillon [this message]
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=20171218220719.15339f2d@bbrezillon \
    --to=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=richard@nod.at \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox