From: Dave Jones <davej@codemonkey.org.uk>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Ross Maynard <bids.7405@bigpond.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
Linux Networking <netdev@vger.kernel.org>,
Linux USB <linux-usb@vger.kernel.org>,
Oliver Neukum <oneukum@suse.com>
Subject: Re: Fwd: 3 more broken Zaurii - SL-5600, A300, C700
Date: Thu, 6 Jul 2023 12:41:05 -0400 [thread overview]
Message-ID: <ZKbuoRBi50i8OZ9d@codemonkey.org.uk> (raw)
In-Reply-To: <e1fdc435-089c-8ce7-d536-ce3780a4ba95@leemhuis.info>
On Thu, Jul 06, 2023 at 01:45:57PM +0200, Thorsten Leemhuis wrote:
> On 06.07.23 05:08, Bagas Sanjaya wrote:
> >>
> >> I notice a regression report on Bugzilla [1]. Quoting from it:
> >>
> >>> The following patch broke support of 3 more Zaurus models: SL-5600, A300 and C700
> >>>
> >>> [16adf5d07987d93675945f3cecf0e33706566005] usbnet: Remove over-broad module alias from zaurus
>
> ...
> He sometimes shows up on Linux kernel lists, but I doubt he cares about
> that change after all these years. And I would not blame him at all.
That's about the size of it. This is pretty near the bottom of my ever-shrinking
list of kernel drivers I care about.
> Yes, we have the "no regressions" rule, but contributing a change to the
> kernel OTOH should not mean that you are responsible for all regressions
> it causes for your whole life. :-)
That said, 12 years later, 16adf5d07987d93675945f3cecf0e33706566005
is still the right thing to do. Adding actual matches for the devices
rather than matching by class will prevent this getting loaded where it
doesn't need to be.
If someone actually cares to get this working, cargo-culting Oliver's
change to add the extra id is likely the way forward.
Dave
next prev parent reply other threads:[~2023-07-06 17:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-05 2:09 Fwd: 3 more broken Zaurii - SL-5600, A300, C700 Bagas Sanjaya
2023-07-06 3:08 ` Bagas Sanjaya
2023-07-06 11:45 ` Thorsten Leemhuis
2023-07-06 16:41 ` Dave Jones [this message]
2023-07-07 12:28 ` Ross Maynard
2023-07-08 12:17 ` Ross Maynard
2023-07-08 20:49 ` Andrew Lunn
2023-07-09 4:36 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-10 16:55 ` Jakub Kicinski
2023-07-10 17:09 ` Linux regression tracking (Thorsten Leemhuis)
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=ZKbuoRBi50i8OZ9d@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--cc=bagasdotme@gmail.com \
--cc=bids.7405@bigpond.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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).