linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] MAINTAINERS: update entry for atmel_serial driver
Date: Thu, 29 Sep 2016 10:05:58 +0200	[thread overview]
Message-ID: <20160929080557.GA3406@kroah.com> (raw)
In-Reply-To: <3dc3a39b-5cae-1ad1-df44-bed4703121c3@atmel.com>

On Thu, Sep 29, 2016 at 09:37:46AM +0200, Nicolas Ferre wrote:
> 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.

It's ok, I've fixed it up by hand, it's a tough file to handle at times
with lots of different trees touching it like you mention.

greg k-h

      reply	other threads:[~2016-09-29  8:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28 15:47 [PATCH] MAINTAINERS: update entry for atmel_serial driver 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
2016-09-29  8:05     ` Greg Kroah-Hartman [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=20160929080557.GA3406@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).