All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Michael Walle <michael@walle.cc>
Cc: Matus Ujhelyi <ujhelyi.m@gmail.com>,
	acmattheis@gmx.net,
	Christoph Mattheis <christoph.mattheis@arcor.de>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: Broken ethernet on SolidRun cubox-i
Date: Fri, 8 Jan 2021 12:37:16 +0000	[thread overview]
Message-ID: <20210108123716.GX1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <1ed4a0ffc17a827240706ed3fa28cd2a@walle.cc>

On Fri, Jan 08, 2021 at 01:14:19PM +0100, Michael Walle wrote:
> Am 2021-01-08 13:01, schrieb Russell King - ARM Linux admin:
> > This sounds like a mess of indirection. What is "Christophs dtb"?
> > Why are there different dtbs out there for the same platform? If
> > there's changes necessary, why aren't they being submitted to the
> > mainline kernel?
> > 
> > In fact, why aren't users reporting these problems to mainline kernel
> > developers? Why do we have to have this tortuous bug reporting route
> > which makes testing fixes difficult?
> > 
> > This rather makes me not want to care about this.
> 
> Well first it was a suspected issue with 'my' change in the Atheros
> PHY driver, which turned out to be not the case. I _voluntarily_
> tried to debug the issue with a user (Christoph) just to find out
> that it is likely caused by the commit mentioned above. So for
> startes, why would I care? I just wanted to be kind and provide
> some help. If anything, this shows me, I should rather stick to
> my own problems.
> 
> So please advise Christoph, where he should report this bug.

There is, unfortunately, a long history where the appropriate kernel
developers have had no knowledge of bugs that have been introduced
by changes that have been made, simply because users report them on
things like web forums or other mailing lists.

In the normal process of things, the bugs have only found out about
years later, maybe when someone finally contacts the appropriate
kernel developers pointing out the problem.

A case in point was the removal of bogomips from /proc/cpuinfo, which
resulted in kernel developers being roasted by Linus when it was
pointed out that users had been reporting the problem on forums for
over a year. Apparently, it was _our_ fault for not knowing about
them.

Similar seems to be happening with my SFP work - it seems people would
much rather report problems on random forums around the Internet rather
than send an email to anyone who can fix the problem in mainline
kernels.

Kernel development is fundamentally a difficult, frustrating and
depressing activity.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-01-08 12:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-26 12:18 Broken ethernet on SolidRun cubox-i Michael Walle
2020-12-26 12:34 ` Russell King - ARM Linux admin
2020-12-27 15:33   ` Michael Walle
2020-12-27 15:59     ` Michael Walle
2020-12-27 16:11       ` Russell King - ARM Linux admin
2020-12-27 18:07         ` Andrew Lunn
2021-01-08 11:53         ` Russell King - ARM Linux admin
2021-01-08 11:58           ` Michael Walle
2021-01-08 12:01             ` Russell King - ARM Linux admin
2021-01-08 12:14               ` Michael Walle
2021-01-08 12:25                 ` Christoph Mattheis
2021-01-08 12:27                   ` Russell King - ARM Linux admin
2021-01-08 12:33                     ` Christoph Mattheis
2021-01-08 12:37                 ` Russell King - ARM Linux admin [this message]
2021-01-08 12:51                   ` Michael Walle

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=20210108123716.GX1551@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=acmattheis@gmx.net \
    --cc=christoph.mattheis@arcor.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=michael@walle.cc \
    --cc=ujhelyi.m@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.