From: Jakub Kicinski <kuba@kernel.org>
To: Imre Kaloz <kaloz@kernel.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
Lee Jones <lee@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
mfd@lists.linux.dev, linux-serial@vger.kernel.org,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, Damien Le Moal <dlemoal@kernel.org>,
Niklas Cassel <cassel@kernel.org>,
linux-ide@vger.kernel.org, Pavel Machek <pavel@kernel.org>,
linux-leds@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 00/53] MIPS: SGI-IP27: add support for the IP35 (Bedrock hub) machines
Date: Tue, 20 Oct 2026 14:56:11 -0700 [thread overview]
Message-ID: <20261020145611.4e277615@kernel.org> (raw)
In-Reply-To: <20261020204214.28625-1-kaloz@kernel.org>
On Tue, 20 Oct 2026 22:42:13 +0200 Imre Kaloz wrote:
> On Tue, 20 Oct 2026 11:06:19 -0700 Jakub Kicinski wrote:
> > Why do we need support for machines discontinued 20+ years ago?
>
> For netdev the question is smaller than the series: patches 25 and 38,
> 44 lines in ioc3-eth, a driver that is already in tree for the same
> part on IP27 and IP30. Patch 25 is a no-op on both of those (the bit it
> tests is always set behind a classic Bridge); patch 38 is a MAC-address
> fallback. I should have said in the cover that the series is meant to go
> through the MIPS tree and that I'm only after an Ack for those two --
> sorry for the noise on your queue.
>
> As for why at all: same reason IP27, IP30 and IP32 are in tree. The
> hardware is in use, Thomas maintains the platform, and people run and
> test it; "discontinued" has never been the removal criterion, lack of
> maintainers has. IP35 is IP27's direct successor on the same
> Hub/XTalk/Bridge architecture with the same IOC3, plus its successor
> IOC4, so most of the series is teaching existing code about one more
> hub generation. And these boxes still earn their keep as a stress case
> for arch and core code -- e.g. the kmem_cache_destroy() race that just
> turned up on my Ultra 45:
> https://lore.kernel.org/all/atDCYwNfKW3m6YXh@thinkstation/
I don't think you answered my question, or at least I'm too daft
to catch what you mean. IP35 was not supported so nobody is using
it with Linux today. You're adding the support, and since it's
a platform discontinued 20 years ago there's 0 chance of real users
of any of this code.
What am I missing?
prev parent reply other threads:[~2026-10-20 21:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 13:16 [PATCH v2 00/53] MIPS: SGI-IP27: add support for the IP35 (Bedrock hub) machines Imre Kaloz
2026-10-13 13:16 ` [PATCH v2 01/53] MIPS: PCI: xtalk-bridge: refuse device numbers past the last slot Imre Kaloz
2026-10-13 13:16 ` [PATCH v2 02/53] MIPS: PCI: xtalk-bridge: assign slots the PROM leaves unconfigured Imre Kaloz
2026-10-13 13:16 ` [PATCH v2 03/53] MIPS: PCI: xtalk-bridge: write a type 1 IOC3 through the type 1 window Imre Kaloz
2026-10-13 13:16 ` [PATCH v2 04/53] MIPS: PCI: xtalk-bridge: flush config space writes Imre Kaloz
2026-10-13 13:16 ` [PATCH v2 05/53] MIPS: PCI: xtalk-bridge: reassign slots whose devio window maps elsewhere Imre Kaloz
2026-10-13 13:16 ` [PATCH v2 26/53] MIPS: SGI-IP27: pick the XBridge and PIC DMA address form by mask Imre Kaloz
2026-10-13 13:35 ` [PATCH v2 00/53] MIPS: SGI-IP27: add support for the IP35 (Bedrock hub) machines Niklas Cassel
2026-10-13 14:25 ` Imre Kaloz
2026-10-20 18:06 ` Jakub Kicinski
2026-10-20 20:42 ` Imre Kaloz
2026-10-20 21:56 ` Jakub Kicinski [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=20261020145611.4e277615@kernel.org \
--to=kuba@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=andrew+netdev@lunn.ch \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=davem@davemloft.net \
--cc=dlemoal@kernel.org \
--cc=edumazet@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=jirislaby@kernel.org \
--cc=kaloz@kernel.org \
--cc=lee@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavel@kernel.org \
--cc=tsbogend@alpha.franken.de \
/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