All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rich Felker <dalias@libc.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Christoph Hellwig <hch@infradead.org>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-sh@vger.kernel.org, ysato@users.sourceforge.jp,
	linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
	Rob Landley <rob@landley.net>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] sh: remove sh5 support
Date: Fri, 05 Jun 2020 15:43:44 +0000	[thread overview]
Message-ID: <20200605154343.GU1079@brightrain.aerifal.cx> (raw)
In-Reply-To: <0af28795-b27a-2dd9-0d0f-c2a8d4b8d512@physik.fu-berlin.de>

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\x158429470120959&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\x158429470221261&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

WARNING: multiple messages have this Message-ID (diff)
From: Rich Felker <dalias@libc.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Christoph Hellwig <hch@infradead.org>,
	Arnd Bergmann <arnd@arndb.de>,
	linux-sh@vger.kernel.org, ysato@users.sourceforge.jp,
	linux-kernel@vger.kernel.org, viro@zeniv.linux.org.uk,
	Rob Landley <rob@landley.net>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] sh: remove sh5 support
Date: Fri, 5 Jun 2020 11:43:44 -0400	[thread overview]
Message-ID: <20200605154343.GU1079@brightrain.aerifal.cx> (raw)
In-Reply-To: <0af28795-b27a-2dd9-0d0f-c2a8d4b8d512@physik.fu-berlin.de>

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

  reply	other threads:[~2020-06-05 15:43 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 22:19 [GIT PULL] sh: remove sh5 support Arnd Bergmann
2020-04-24 22:19 ` Arnd Bergmann
2020-04-24 22:19 ` [PATCH 1/1] " Arnd Bergmann
2020-04-24 22:19   ` Arnd Bergmann
2020-05-07 14:35 ` [GIT PULL] " Christoph Hellwig
2020-05-07 14:35   ` Christoph Hellwig
2020-05-28  5:46   ` Christoph Hellwig
2020-05-28  5:46     ` Christoph Hellwig
2020-05-28  5:55     ` John Paul Adrian Glaubitz
2020-05-28  5:55       ` John Paul Adrian Glaubitz
2020-05-28  9:40       ` Rob Landley
2020-05-28  9:40         ` Rob Landley
2020-05-28 16:14     ` Rich Felker
2020-05-28 16:14       ` Rich Felker
2020-05-28 22:14       ` Rich Felker
2020-05-28 22:14         ` Rich Felker
2020-05-28 22:28         ` Rob Landley
2020-05-28 22:28           ` Rob Landley
2020-05-28 22:32         ` John Paul Adrian Glaubitz
2020-05-28 22:32           ` John Paul Adrian Glaubitz
2020-05-28 22:37           ` Rich Felker
2020-05-28 22:37             ` Rich Felker
2020-05-29 14:35         ` Christoph Hellwig
2020-05-29 14:35           ` Christoph Hellwig
2020-05-29 14:30       ` Christoph Hellwig
2020-05-29 14:30         ` Christoph Hellwig
2020-05-29 17:53         ` Rich Felker
2020-05-29 17:53           ` Rich Felker
2020-05-29 18:22           ` Christoph Hellwig
2020-05-29 18:22             ` Christoph Hellwig
2020-05-30  8:08           ` John Paul Adrian Glaubitz
2020-05-30  8:08             ` John Paul Adrian Glaubitz
2020-05-30  8:47             ` Geert Uytterhoeven
2020-05-30  8:47               ` Geert Uytterhoeven
2020-05-31  3:20             ` Rob Landley
2020-05-31  3:20               ` Rob Landley
2020-05-31  8:03               ` John Paul Adrian Glaubitz
2020-05-31  8:03                 ` John Paul Adrian Glaubitz
2020-06-01  2:55                 ` Rich Felker
2020-06-01  2:55                   ` Rich Felker
2020-06-01  8:16                   ` John Paul Adrian Glaubitz
2020-06-01  8:16                     ` John Paul Adrian Glaubitz
2020-06-01 18:13             ` Rich Felker
2020-06-01 18:13               ` Rich Felker
2020-06-01 21:12               ` Arnd Bergmann
2020-06-01 21:12                 ` Arnd Bergmann
2020-06-02  1:33               ` Rich Felker
2020-06-02  1:33                 ` Rich Felker
2020-06-02  2:49                 ` Andrew Morton
2020-06-02  2:49                   ` Andrew Morton
2020-06-02  2:53                   ` Rich Felker
2020-06-02  2:53                     ` Rich Felker
2020-06-03  7:27                 ` John Paul Adrian Glaubitz
2020-06-03  7:27                   ` John Paul Adrian Glaubitz
2020-06-03  7:31                   ` John Paul Adrian Glaubitz
2020-06-03  7:31                     ` John Paul Adrian Glaubitz
2020-06-05 15:38                 ` John Paul Adrian Glaubitz
2020-06-05 15:38                   ` John Paul Adrian Glaubitz
2020-06-05 15:43                   ` Rich Felker [this message]
2020-06-05 15:43                     ` Rich Felker
2020-06-05 15:47                     ` John Paul Adrian Glaubitz
2020-06-05 15:47                       ` John Paul Adrian Glaubitz
2020-06-05 15:59                       ` Rich Felker
2020-06-05 15:59                         ` Rich Felker
2020-06-05 17:58                         ` John Paul Adrian Glaubitz
2020-06-05 17:58                           ` John Paul Adrian Glaubitz
2020-06-05 18:23                           ` Geert Uytterhoeven
2020-06-05 18:23                             ` Geert Uytterhoeven
2020-06-06  0:50                             ` Andrew Morton
2020-06-06  0:50                               ` Andrew Morton

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=20200605154343.GU1079@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=geert@linux-m68k.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=rob@landley.net \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.