From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
<richard.genoud@gmail.com>, <jslaby@suse.cz>,
<linux-serial@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
Cyrille Pitchen <cyrille.pitchen@atmel.com>
Subject: Re: [PATCH] MAINTAINERS: update entry for atmel_serial driver
Date: Thu, 29 Sep 2016 09:37:46 +0200 [thread overview]
Message-ID: <3dc3a39b-5cae-1ad1-df44-bed4703121c3@atmel.com> (raw)
In-Reply-To: <20160929063148.GA418@kroah.com>
Le 29/09/2016 à 08:31, Greg Kroah-Hartman a écrit :
> On Wed, Sep 28, 2016 at 05:47:35PM +0200, Nicolas Ferre wrote:
>> Change maintainer for the serial driver found on most of the
>> Microchip / Atmel MPUs and take advantage of the move to rename
>> and reorder the entry.
>> I'm happy that Richard is taking over the maintenance of this
>> driver.
>>
>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
>> Acked-by: Richard Genoud <richard.genoud@gmail.com>
>> ---
>> MAINTAINERS | 11 ++++++-----
>> 1 file changed, 6 insertions(+), 5 deletions(-)
>
> This doesn't apply to my tty-next tree at all, what did you make it
> against?
Yesterdays' linux-next (next-20160928 tag). I thought it would be the
best for easy pick-up by anybody, particularly on a highly shared file
like MAINTAINERS.
Tell me if you want me to collect all tags, rebase on tty-next and re-send.
--
Nicolas Ferre
next prev parent reply other threads:[~2016-09-29 7:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 15:47 Nicolas Ferre
2016-09-28 15:52 ` Greg Kroah-Hartman
2016-09-28 15:57 ` Richard Genoud
2016-09-28 16:04 ` Joe Perches
2016-09-29 6:17 ` Richard Genoud
2016-09-29 6:31 ` Greg Kroah-Hartman
2016-09-29 7:37 ` Nicolas Ferre [this message]
2016-09-29 8:05 ` Greg Kroah-Hartman
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=3dc3a39b-5cae-1ad1-df44-bed4703121c3@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=cyrille.pitchen@atmel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=richard.genoud@gmail.com \
/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
all inboxes | Powered by JetHome®