From: Florian Fainelli <f.fainelli@gmail.com>
To: James Hogan <jhogan@kernel.org>,
linux-mips@linux-mips.org, Ralf Baechle <ralf@linux-mips.org>
Cc: Paul Burton <paul.burton@mips.com>,
David Daney <david.daney@cavium.com>,
John Crispin <john@phrozen.org>,
Matt Redfearn <matt.redfearn@mips.com>
Subject: Re: [PATCH] MAINTAINERS: Add James as MIPS co-maintainer
Date: Fri, 5 Jan 2018 16:53:29 -0800 [thread overview]
Message-ID: <ddd06175-24e8-7bd5-e938-b817ab4c26d3@gmail.com> (raw)
In-Reply-To: <20180105213647.28850-1-jhogan@kernel.org>
On 01/05/2018 01:36 PM, James Hogan wrote:
> I've been taking on some co-maintainer duties already, so lets make it
> official in the MAINTAINERS file.
>
> Link: https://lkml.kernel.org/r/33db77a2-32e4-6b2c-d463-9d116ba55623@imgtec.com
> Link: https://lkml.kernel.org/r/20171207110549.GM27409@jhogan-linux.mipstec.com
> Signed-off-by: James Hogan <jhogan@kernel.org>
> Cc: Ralf Baechle <ralf@linux-mips.org>
> Cc: Paul Burton <paul.burton@mips.com>
> Cc: David Daney <david.daney@cavium.com>
> Cc: John Crispin <john@phrozen.org>
> Cc: Florian Fainelli <f.fainelli@gmail.com>
> Cc: Matt Redfearn <matt.redfearn@mips.com>
> Cc: linux-mips@linux-mips.org
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
Thanks James!
--
Florian
next prev parent reply other threads:[~2018-01-06 0:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 21:36 [PATCH] MAINTAINERS: Add James as MIPS co-maintainer James Hogan
2018-01-05 21:56 ` Paul Burton
2018-01-05 21:56 ` Paul Burton
2018-01-05 22:07 ` Aaro Koskinen
2018-01-05 22:34 ` David Daney
2018-01-06 0:53 ` Florian Fainelli [this message]
2018-01-08 8:55 ` Matt Redfearn
2018-01-08 8:55 ` Matt Redfearn
-- strict thread matches above, loose matches on Subject: below --
2017-08-30 10:49 Maintenance of Linux/MIPS? Matt Redfearn
2017-09-02 19:34 ` [PATCH] MAINTAINERS: Add James as MIPS co-maintainer Florian Fainelli
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=ddd06175-24e8-7bd5-e938-b817ab4c26d3@gmail.com \
--to=f.fainelli@gmail.com \
--cc=david.daney@cavium.com \
--cc=jhogan@kernel.org \
--cc=john@phrozen.org \
--cc=linux-mips@linux-mips.org \
--cc=matt.redfearn@mips.com \
--cc=paul.burton@mips.com \
--cc=ralf@linux-mips.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