From: Andrew Morton <akpm@linux-foundation.org>
To: Rich Felker <dalias@libc.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
"D. Jeff Dionne" <jeff@uClinux.org>,
Rob Landley <rob@landley.net>,
Peter Zijlstra <peterz@infradead.org>,
Simon Horman <horms+renesas@verge.net.au>,
Geert Uytterhoeven <geert+renesas@glider.be>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: return arch/sh to maintained state, with new maintainers
Date: Fri, 22 Jan 2016 21:08:52 +0000 [thread overview]
Message-ID: <20160122130852.1c9153fe74546f6e391f8d97@linux-foundation.org> (raw)
In-Reply-To: <20160122052614.GA21960@brightrain.aerifal.cx>
On Fri, 22 Jan 2016 00:26:15 -0500 Rich Felker <dalias@libc.org> wrote:
> From: Rich Felker <dalias@libc.org>
>
> Add Yoshinori Sato and Rich Felker as maintainers for arch/sh
> (SUPERH).
>
> Signed-off-by: Rich Felker <dalias@libc.org>
> Signed-off-by: Yoshinori Sato <ysato@users.sourceforge.jp>
> Acked-by: D. Jeff Dionne <jeff@uClinux.org>
> Acked-by: Rob Landley <rob@landley.net>
> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> Acked-by: Simon Horman <horms+renesas@verge.net.au>
> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
>
> ---
>
> Andrew, since we don't have our own repo up for Linus to pull from
> yet, could you commit this? Geert (who's the closest there is to an
> acting maintainer for sh right now) and I thought that would make the
> most sense. If possible I'd really like to get this in the merge
> window to make it official that sh isn't abandoned.
No probs. I'll cc:stable as well, so you get bug reports for older
kernel versions :)
prev parent reply other threads:[~2016-01-22 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 5:26 [PATCH] MAINTAINERS: return arch/sh to maintained state, with new maintainers Rich Felker
2016-01-22 21:08 ` Andrew Morton [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=20160122130852.1c9153fe74546f6e391f8d97@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dalias@libc.org \
--cc=geert+renesas@glider.be \
--cc=horms+renesas@verge.net.au \
--cc=jeff@uClinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rob@landley.net \
--cc=ysato@users.sourceforge.jp \
/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).