From: Christoph Hellwig <hch@infradead.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch <linux-arch@vger.kernel.org>,
"moderated list:H8/300 ARCHITECTURE"
<uclinux-h8-devel@lists.sourceforge.jp>
Subject: Re: [RFC PULL] remove arch/h8300
Date: Sun, 3 Apr 2022 05:43:51 -0700 [thread overview]
Message-ID: <YkmWh2tss8nXKqc5@infradead.org> (raw)
In-Reply-To: <CAK8P3a1dUVsZzhAe81usLSkvH29zHgiV9fhEkWdq7_W+nQBWbg@mail.gmail.com>
On Tue, Mar 08, 2022 at 09:19:16AM +0100, Arnd Bergmann wrote:
> If there are no other objections, I'll just queue this up for 5.18 in
> the asm-generic
> tree along with the nds32 removal.
So it is the last day of te merge window and arch/h8300 is till there.
And checking nw the removal has also not made it to linux-next. Looks
like it is so stale that even the removal gets ignored :(
next prev parent reply other threads:[~2022-04-03 12:43 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 6:52 [RFC PULL] remove arch/h8300 Christoph Hellwig
2022-03-08 8:19 ` Arnd Bergmann
2022-04-03 12:43 ` Christoph Hellwig [this message]
2022-04-04 13:07 ` Arnd Bergmann
2022-04-04 13:09 ` John Paul Adrian Glaubitz
2022-04-04 13:22 ` Geert Uytterhoeven
2022-04-04 23:34 ` Damien Le Moal
2022-04-06 21:25 ` Rob Landley
2022-04-07 7:17 ` Arnd Bergmann
2022-04-07 7:47 ` John Paul Adrian Glaubitz
2022-04-07 7:52 ` Christoph Hellwig
2022-04-07 8:34 ` Finn Thain
2022-04-04 13:41 ` Greg Ungerer
2022-04-05 3:23 ` Daniel Palmer
2022-04-05 13:07 ` Greg Ungerer
2022-04-09 0:24 ` Rob Landley
2022-04-09 1:59 ` Finn Thain
2022-04-09 4:18 ` Greg Ungerer
2022-04-10 7:26 ` Rob Landley
2022-04-10 8:08 ` Rob Landley
2022-04-14 0:49 ` Greg Ungerer
2022-04-09 3:37 ` Daniel Palmer
2022-04-10 7:13 ` Rob Landley
2022-04-09 4:14 ` Greg Ungerer
2022-04-04 17:57 ` Max Filippov
2022-04-04 19:01 ` Arnd Bergmann
2022-04-04 19:14 ` Max Filippov
2022-04-04 19:35 ` Arnd Bergmann
2022-04-04 19:44 ` Arnd Bergmann
2022-04-04 20:56 ` Max Filippov
2022-04-04 20:48 ` Max Filippov
2022-04-04 23:32 ` Damien Le Moal
2022-04-05 21:26 ` Guenter Roeck
2022-04-05 22:01 ` Arnd Bergmann
2022-04-06 0:12 ` Guenter Roeck
2022-05-06 14:07 ` Geert Uytterhoeven
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=YkmWh2tss8nXKqc5@infradead.org \
--to=hch@infradead.org \
--cc=arnd@arndb.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=uclinux-h8-devel@lists.sourceforge.jp \
--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).