[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200605154343.GU1079@brightrain.aerifal.cx>
Date: Fri, 5 Jun 2020 11:43:44 -0400
From: Rich Felker <dalias@...c.org>
To: John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
Cc: Christoph Hellwig <hch@...radead.org>,
Arnd Bergmann <arnd@...db.de>, linux-sh@...r.kernel.org,
ysato@...rs.sourceforge.jp, linux-kernel@...r.kernel.org,
viro@...iv.linux.org.uk, Rob Landley <rob@...dley.net>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] sh: remove sh5 support
On Fri, Jun 05, 2020 at 05:38:18PM +0200, John Paul Adrian Glaubitz wrote:
> Hi Rich!
>
> On 6/2/20 3:33 AM, Rich Felker wrote:
> >>>> [PATCH 1/2] arch/sh: vmlinux.scr
> >>>> https://marc.info/?l=linux-sh&m=158429470120959&w=2
> >>
> >> OK.
> >
> > Included in -mm.
>
> I just had a look at your tree and it looks you forgot to merge the second
> patch of the series, see:
>
> > https://marc.info/?l=linux-sh&m=158429470221261&w=2
>
> Can you include the patch as well?
This one is outside arch/sh and I'm not sure it's permissible to go up
through my tree. I was also under the impression that only part 1 was
needed to fix the immediate problem on sh and tha part 2 was for
completeness and to make sure the same doesn't happen on other archs
in the future, but maybe my understanding here is incorrect.
> And would it be okay to send a PR to Linus
> after that?
Sure, will do right away once we resolve what to do with the above,
and provided you don't have anything else you want me to evaluate for
inclusion.
Rich
Powered by blists - more mailing lists