Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
MIME-Version: 1.0
References: <20211005001914.28574-1-rdunlap@infradead.org> <20211005001914.28574-3-rdunlap@infradead.org>
 <20211027205431.GX7074@brightrain.aerifal.cx> <CAMuHMdWUQkhYxXfrG4MG-Ghi62P_XVxkCMb_6qijP-MMgn-JWg@mail.gmail.com>
 <20211028133049.GY7074@brightrain.aerifal.cx>
In-Reply-To: <20211028133049.GY7074@brightrain.aerifal.cx>
From:   Geert Uytterhoeven <geert@linux-m68k.org>
Date:   Thu, 28 Oct 2021 15:37:47 +0200
Message-ID: <CAMuHMdUw=6RMF4gEhROMBwQALNmmKJgiKQLYymV4m75EZV+DJQ@mail.gmail.com>
Subject: Re: [PATCH 2/5 v3] sh: add git tree to MAINTAINERS
To:     Rich Felker <dalias@libc.org>
Cc:     Randy Dunlap <rdunlap@infradead.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Yoshinori Sato <ysato@users.sourceforge.jp>,
        Linux-sh list <linux-sh@vger.kernel.org>,
        John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
        Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hi Rich,

CC Konstantin

On Thu, Oct 28, 2021 at 3:30 PM Rich Felker <dalias@libc.org> wrote:
> On Thu, Oct 28, 2021 at 10:33:54AM +0200, Geert Uytterhoeven wrote:
> > On Wed, Oct 27, 2021 at 10:54 PM Rich Felker <dalias@libc.org> wrote:
> > > On Mon, Oct 04, 2021 at 05:19:11PM -0700, Randy Dunlap wrote:
> > > > Add the git tree location for linux-sh.
> > > >
> > > > Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> >
> > > > --- linux-next-20211001.orig/MAINTAINERS
> > > > +++ linux-next-20211001/MAINTAINERS
> > > > @@ -18047,6 +18047,7 @@ M:    Yoshinori Sato <ysato@users.sourcefor
> > > >  M:   Rich Felker <dalias@libc.org>
> > > >  L:   linux-sh@vger.kernel.org
> > > >  S:   Maintained
> > > > +T:   git git://git.libc.org/linux-sh
> > > >  Q:   http://patchwork.kernel.org/project/linux-sh/list/
> > > >  F:   Documentation/sh/
> > > >  F:   arch/sh/
> > >
> > > I'm omitting this for now since (as noted on the cgit description)
> > > this server is not provisioned adequately for cloning from scratch,
> > > and should only be used for fetch into an already-populated mainline
> > > repo clone. If that's a problem I can see about getting it moved
> > > somewhere more appropriate.
> >
> > Perhaps you can move it to kernel.org?
>
> I would love to. This was my hope years ago, but I got bogged down in
> the GPG key signing requirements and folks not following through with
> signing my key. Has any of that been streamlined since?

I'll let Konstantin respond...

> > > The rest of this series should appear in next shortly.
> >
> > Thanks a lot!
>
> Looks like it's been pulled by next now with no reports of anything
> going wrong. I know it's late in the release cycle but should I

Good!

> probably go ahead and send a PR?

Actually you're right on time ;-)
Your tree is based on v5.15-rc1, and the merge window for v5.16 is
expected to open on Monday. So you can send the PR right away.

Thanks!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds