From: Jakub Kicinski <kuba@kernel.org>
To: "Maciej W. Rozycki" <macro@orcam.me.uk>
Cc: Imre Kaloz <kaloz@kernel.org>,
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: Thu, 22 Oct 2026 14:34:40 -0700 [thread overview]
Message-ID: <20261022143440.4ddae87e@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.21.2610222009000.22065@angie.orcam.me.uk>
On Thu, 22 Oct 2026 20:28:25 +0100 (BST) Maciej W. Rozycki wrote:
> On Wed, 21 Oct 2026, Jakub Kicinski wrote:
> > > The users are the people running these machines, the same population
> > > as for IP27 and IP30, and the ioc3-eth driver in net/ exists for them
> > > today. The series was developed and tested on a Fuel and a Tezro in
> > > regular use, so "nobody is using it with Linux" is true only in the
> > > sense that the support isn't merged yet; that was equally true of IP30
> > > when it went in for 5.5, and of every port before it.
> >
> > Not sure if you followed the discussions at the recent maintainer
> > summit but we are now allowed to be more opinionated about code
> > we merge. Merging code just to test that code seems like entertainment
> > for the authors, not useful development.
>
> I thought the event was by invitation only.
LWN posts a great summary.
> Anyway, this seems to me like discouraging enthusiasts who do their work
> outside their day job from making contributions. Their natural target are
> commercially worthless systems, since working for free on commercially
> valuable systems would be taking away someone's bread and I think grossly
> undeserved support for corporations. Taking this stance effectively would
> be cutting Linux off from its origins and making it a commercial project.
Or. Perhaps. By pushing this useless retro-hobbist hogwash you're
contributing to the burn out of genuine maintainers, pushing the
project into the hands of people who do have anterior motives.
Who is to say..
> Please let's not go down this route and only base the acceptance, or not,
> of submissions on quality merits. Many of us took this route to Linux, by
> showing competence in public with work done for free, and some of us still
> enjoy such side project even if we do have a day job now that involves
> Linux development. Let's not close this option to people.
Who cares about quality of code nobody will run?
prev parent reply other threads:[~2026-10-22 21:34 UTC|newest]
Thread overview: 13+ 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 31/53] mfd: ioc3: Add support for IOC4 Imre Kaloz
2026-10-20 12:02 ` Lee Jones
2026-10-20 21:07 ` 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
2026-10-21 9:05 ` Imre Kaloz
2026-10-21 14:39 ` Jakub Kicinski
2026-10-22 19:28 ` Maciej W. Rozycki
2026-10-22 21:34 ` 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=20261022143440.4ddae87e@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=macro@orcam.me.uk \
--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