Linux RTC
 help / color / mirror / Atom feed
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: Wed, 21 Oct 2026 07:39:21 -0700	[thread overview]
Message-ID: <20261021073921.07632a37@kernel.org> (raw)
In-Reply-To: <20261021090556.21168-1-kaloz@kernel.org>

On Wed, 21 Oct 2026 11:05:55 +0200 Imre Kaloz wrote:
> On Tue, 20 Oct 2026 14:56:11 -0700 Jakub Kicinski wrote:
> > 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?  
> 
> 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.

> The kernel's test for a platform isn't commercial relevance, it's a
> maintainer, which Thomas is, and testers, which this series has. If
> netdev doesn't want to spend time on it, say so and I'll ask Thomas to
> take the two ioc3-eth patches through the MIPS tree.

Not how subsystem boundaries work. You have to repost the two
networking patches to get them merged via net-next. Our CIs
will not trigger for partial posting to netdev.

      reply	other threads:[~2026-10-21 14:39 UTC|newest]

Thread overview: 11+ 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 30/53] rtc: m48t35: support the SGI IP35 timekeeper's 1968 year base Imre Kaloz
2026-10-13 14:28   ` Alexandre Belloni
2026-10-16 23:09     ` 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 [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=20261021073921.07632a37@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