linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Rich Felker <dalias@libc.org>
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>
Subject: Re: [GIT PULL] sh: remove sh5 support
Date: Fri, 29 May 2020 14:30:59 +0000	[thread overview]
Message-ID: <20200529143059.GA25475@infradead.org> (raw)
In-Reply-To: <20200528161416.GY1079@brightrain.aerifal.cx>

On Thu, May 28, 2020 at 12:14:16PM -0400, Rich Felker wrote:
> It is in active use. Please do not act on such a request. I would be
> much quicker to ack things that actually need ack if I weren't CC'd on
> hundreds of random non-arch-specific changes that don't need it, but I
> understand that's how the kernel process works. If there are things
> that need ack please feel free to ping.
> 
> Note that I specifically acked and requested the sh5 removal.

But you did not actually pick it up - because of that it still isn't
in linux-next and thus most likely will miss Linux 5.8.

  parent reply	other threads:[~2020-05-29 14:30 UTC|newest]

Thread overview: 35+ 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 ` [PATCH 1/1] " Arnd Bergmann
2020-05-07 14:35 ` [GIT PULL] " Christoph Hellwig
2020-05-28  5:46   ` Christoph Hellwig
2020-05-28  5:55     ` John Paul Adrian Glaubitz
2020-05-28  9:40       ` Rob Landley
2020-05-28 16:14     ` Rich Felker
2020-05-28 22:14       ` Rich Felker
2020-05-28 22:28         ` Rob Landley
2020-05-28 22:32         ` John Paul Adrian Glaubitz
2020-05-28 22:37           ` Rich Felker
2020-05-29 14:35         ` Christoph Hellwig
2020-05-29 14:30       ` Christoph Hellwig [this message]
2020-05-29 17:53         ` Rich Felker
2020-05-29 18:22           ` Christoph Hellwig
2020-05-30  8:08           ` John Paul Adrian Glaubitz
2020-05-30  8:47             ` Geert Uytterhoeven
2020-05-31  3:20             ` Rob Landley
2020-05-31  8:03               ` John Paul Adrian Glaubitz
2020-06-01  2:55                 ` Rich Felker
2020-06-01  8:16                   ` John Paul Adrian Glaubitz
2020-06-01 18:13             ` Rich Felker
2020-06-01 21:12               ` Arnd Bergmann
2020-06-02  1:33               ` Rich Felker
2020-06-02  2:49                 ` Andrew Morton
2020-06-02  2:53                   ` Rich Felker
2020-06-03  7:27                 ` 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:43                   ` Rich Felker
2020-06-05 15:47                     ` John Paul Adrian Glaubitz
2020-06-05 15:59                       ` Rich Felker
2020-06-05 17:58                         ` John Paul Adrian Glaubitz
2020-06-05 18:23                           ` Geert Uytterhoeven
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=20200529143059.GA25475@infradead.org \
    --to=hch@infradead.org \
    --cc=arnd@arndb.de \
    --cc=dalias@libc.org \
    --cc=geert@linux-m68k.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 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).