linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: Add mediatek git repository
Date: Thu, 20 Jul 2017 15:18:09 +0200	[thread overview]
Message-ID: <20170720131809.GA19088@kroah.com> (raw)
In-Reply-To: <a0602546-11b4-87be-c738-9539208ce8cb@gmail.com>

On Thu, Jul 20, 2017 at 12:18:10PM +0200, Matthias Brugger wrote:
> On 06/09/2017 10:43 AM, Matthias Brugger wrote:
> > Mediatek repository lives in github for quite a while.
> > Add the repository to the file.
> > 
> > Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
> > ---
> >   MAINTAINERS | 1 +
> >   1 file changed, 1 insertion(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index f7d568b8f133..41410639f650 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -1554,6 +1554,7 @@ M:	Matthias Brugger <matthias.bgg@gmail.com>
> >   L:	linux-arm-kernel at lists.infradead.org (moderated for non-subscribers)
> >   L:	linux-mediatek at lists.infradead.org (moderated for non-subscribers)
> >   S:	Maintained
> > +T:	git https://github.com/mbgg/linux-mediatek.git for-next
> >   F:	arch/arm/boot/dts/mt6*
> >   F:	arch/arm/boot/dts/mt7*
> >   F:	arch/arm/boot/dts/mt8*
> > 
> 
> 
> Looks like this got forgotten for v4.13-rc1.
> Shall I take it through my tree for the next merge window?

Take it now, no reason an update can't go in now.

But why are you not using kernel.org?  Using github for kernel code is a
pain and discouraged.

thanks,

greg k-h

      reply	other threads:[~2017-07-20 13:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-09  8:43 [PATCH] MAINTAINERS: Add mediatek git repository Matthias Brugger
2017-07-20 10:18 ` Matthias Brugger
2017-07-20 13:18   ` Greg KH [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=20170720131809.GA19088@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 NNTP newsgroup(s).