mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Rich Felker <dalias@libc.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	Simon Horman <horms@verge.net.au>,
	Peter Zijlstra <peterz@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"D. Jeff Dionne" <jeff@uclinux.org>,
	Rob Landley <rob@landley.net>
Subject: Re: [PATCH 1/2] MAINTAINERS: return arch/sh to maintained state, with new maintainers
Date: Sat, 16 Jan 2016 21:32:47 -0500	[thread overview]
Message-ID: <20160117023247.GJ238@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAMuHMdVWtxq+62Uz1xqzrnmjor2aOKnxsirSerXhiwh=UfTKiQ@mail.gmail.com>

On Fri, Jan 15, 2016 at 10:31:13AM +0100, Geert Uytterhoeven wrote:
> Hi Rich, Sato-san,
> 
> On Fri, Jan 15, 2016 at 1:52 AM, Rich Felker <dalias@libc.org> wrote:
> > On Wed, Jan 13, 2016 at 10:40:46AM +0900, Simon Horman wrote:
> >> On Mon, Jan 11, 2016 at 06:53:07PM +0100, Peter Zijlstra wrote:
> >> > On Thu, Jan 07, 2016 at 11:39:59PM -0500, Rich Felker 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>
> >> >
> >> > A much appreciated move,
> >> >
> >> > Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> >>
> >> Likewise,
> >>
> >> Acked-by: Simon Horman <horms+renesas@verge.net.au>
> 
> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>

Thanks!

> > While patch 2/2 still seems to need discussion and resolution, I don't
> > think this part (1/2, adding us as maintainers) is controversial. Can
> > it be committed now? Geert? Andrew?
> 
> I think it should go in either through Andrew, or through yourself, depending
> on whether you already have other stuff ready for this merge window, and have
> a git repo to pull from.
> 
> Do you have a git repository to ask Linus to pull from, and to provide a branch
> for linux-next integration testing?

Not quite yet. If it can be done in this merge window, I think it
makes sense for Andrew to do it to make it official that arch/sh isn't
abandoned, and Sato-san and I can have the repo setup well ahead of
the next window. How does that sound?

I'd love it if we could get some of the actual code changes in for
this merge window too but I'm not clear whether there's still time.

Rich

  reply	other threads:[~2016-01-17  2:33 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08  4:39 [PATCH 0/2] Resume maintenance & development of arch/sh Rich Felker
2016-01-08  4:39 ` [PATCH 1/2] MAINTAINERS: return arch/sh to maintained state, with new maintainers Rich Felker
2016-01-11 17:53   ` Peter Zijlstra
2016-01-13  1:40     ` Simon Horman
2016-01-15  0:52       ` Rich Felker
2016-01-15  9:31         ` Geert Uytterhoeven
2016-01-17  2:32           ` Rich Felker [this message]
2016-01-17  8:48             ` Geert Uytterhoeven
2016-01-08  4:40 ` [PATCH 2/2] MAINTAINERS: remove linux-sh list from non-arch/sh sections Rich Felker
2016-01-08  6:56   ` Simon Horman
2016-01-08  9:01     ` Geert Uytterhoeven
2016-01-08 18:21       ` Rich Felker
2016-01-08 20:35         ` Geert Uytterhoeven
2016-01-08 20:52           ` Rich Felker
2016-01-10 19:41             ` Geert Uytterhoeven
2016-01-08 17:35     ` Rob Landley
2016-01-08 18:28       ` Laurent Pinchart
2016-01-08 19:40         ` Rich Felker
2016-01-08 23:15           ` Laurent Pinchart
2016-01-08 22:50         ` Rob Landley
2016-01-10 20:05           ` Geert Uytterhoeven
2016-01-11  2:02             ` Rob Landley
2016-01-11  2:22               ` uClinux.org
2016-01-08 18:51       ` Rich Felker
2016-01-08 18:03   ` Sergei Shtylyov

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=20160117023247.GJ238@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=akpm@linux-foundation.org \
    --cc=geert@linux-m68k.org \
    --cc=horms@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

Powered by JetHome