linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Brugger <matthias.bgg@gmail.com>
To: Olof Johansson <olof@lixom.net>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ARM-SoC Maintainers <arm@kernel.org>,
	"moderated list:ARM/Mediatek SoC..."
	<linux-mediatek@lists.infradead.org>,
	Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Miller <davem@davemloft.net>,
	Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] MAINTAINERS: mediatek: Update SoC entry
Date: Sun, 2 Dec 2018 21:10:27 +0100	[thread overview]
Message-ID: <3de8c309-991f-678c-ccc8-463eff1627e4@gmail.com> (raw)
In-Reply-To: <CAOesGMiE7M_urw2wyeE9gsv6C5xGnFG9uuT+z9rDeoed4mHSUA@mail.gmail.com>



On 02/12/2018 21:03, Olof Johansson wrote:
> On Sun, Dec 2, 2018 at 11:41 AM Matthias Brugger <matthias.bgg@gmail.com> wrote:
>>
>>
>>
>> On 16/10/2018 16:57, Matthias Brugger wrote:
>>> Add IRC channel and URL of the wiki.
>>> Also add soc drivers folder and regex to catch more
>>> mediatek components.
>>>
>>> Signed-off-by: Matthias Brugger <matthias.bgg@gmail.com>
>>> ---
>>
>> Any comments on this patch?
>> Through which tree should it go?
> 
> We can apply it directly, I'll do so on next pass. Patch itself is fine.
> 

Great. Thanks for the feedback :)

Cheers,
Matthias


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2018-12-02 20:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16 14:57 [PATCH] MAINTAINERS: mediatek: Update SoC entry Matthias Brugger
2018-12-02 19:39 ` Matthias Brugger
2018-12-02 20:03   ` Olof Johansson
2018-12-02 20:10     ` Matthias Brugger [this message]
2018-12-03 20:37 ` Olof Johansson

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=3de8c309-991f-678c-ccc8-463eff1627e4@gmail.com \
    --to=matthias.bgg@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=mchehab+samsung@kernel.org \
    --cc=olof@lixom.net \
    /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).