From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
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: Fri, 6 May 2022 16:07:43 +0200 [thread overview]
Message-ID: <CAMuHMdXVS6ROvp4rkZzBOBJBkQYjtdL0-m0ok=8UvTkwp-X4bw@mail.gmail.com> (raw)
In-Reply-To: <Yib9F5SqKda/nH9c@infradead.org>
Hi Chrisoph,
On Tue, Mar 8, 2022 at 12:04 PM Christoph Hellwig <hch@infradead.org> wrote:
> h8300 hasn't been maintained for quite a while, with even years old
> pull request lingering in the old repo. Given that it always was
> rather fringe to start with I'd suggest to go ahead and remove the
> port:
>
> The following changes since commit 5c1ee569660d4a205dced9cb4d0306b907fb7599:
>
> Merge branch 'for-5.17-fixes' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup (2022-02-22 16:14:35 -0800)
>
> are available in the Git repository at:
>
> git://git.infradead.org/users/hch/misc.git remove-h8300
>
> for you to fetch changes up to 1c4b5ecb7ea190fa3e9f9d6891e6c90b60e04f24:
>
> remove the h8300 architecture (2022-02-23 08:52:50 +0100)
>
> ----------------------------------------------------------------
> Christoph Hellwig (1):
> remove the h8300 architecture
>
> .../bindings/clock/renesas,h8300-div-clock.txt | 24 --
> Documentation/devicetree/bindings/h8300/cpu.txt | 13 -
> .../interrupt-controller/renesas,h8300h-intc.txt | 22 --
> .../interrupt-controller/renesas,h8s-intc.txt | 22 --
> .../memory-controllers/renesas,h8300-bsc.yaml | 35 --
More DT bindings to garbage-collect:
Documentation/devicetree/bindings/clock/renesas,h8s2678-pll-clock.txt
Documentation/devicetree/bindings/timer/renesas,16bit-timer.txt
Documentation/devicetree/bindings/timer/renesas,8bit-timer.txt
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
prev parent reply other threads:[~2022-05-06 14:08 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
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 [this message]
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='CAMuHMdXVS6ROvp4rkZzBOBJBkQYjtdL0-m0ok=8UvTkwp-X4bw@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=hch@infradead.org \
--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).