From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Dave Jones <davej@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Ross Maynard <bids.7405@bigpond.com>,
"Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>
Cc: 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>
Subject: Re: Fwd: 3 more broken Zaurii - SL-5600, A300, C700
Date: Thu, 6 Jul 2023 10:08:20 +0700 [thread overview]
Message-ID: <50f4c10d-260c-cb98-e7d2-124f5519fa68@gmail.com> (raw)
In-Reply-To: <7ea9abd8-c35d-d329-f0d4-c8bd220cf691@gmail.com>
On 7/5/23 09:09, Bagas Sanjaya wrote:
> Hi,
>
> 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
>>
>> dmesg and lsusb output attached.
>
> Because the description above was vague, I asked the clarification.
> The reporter replied:
>
>> The problem is that networking to SL-5600 / A300 / C700 devices does not
>> work. I cannot ping the devices.
>>
>> The error is occurring in zaurus.c. dmesg is missing the following line:
>>
>> zaurus 2-2:1.0 usb0: register 'zaurus' at usb-0000:00:1d.0-2,
>> pseudo-MDLM (BLAN) device, 2a:01:39:93:bc:1a
>>
>> A patch was created in 2022 to fix the same problem with the SL-6000:
>>
>> USB: zaurus: support another broken Zaurus -
>> [6605cc67ca18b9d583eb96e18a20f5f4e726103c]
>>
>> Could you please create another patch for the 3 devices: SL-5600 / A300
>> / C700?
>
> See Bugzilla for the full thread and attached dmesg and lsusb.
>
> Dave: The reporter asked to write the quirk for affected devices.
> Would you like to create it?
>
Thorsten: Email to the culprit author (Dave) bounced. What can
I do in this case? Should I start adding get_maintainer.pl output?
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2023-07-06 3:08 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 [this message]
2023-07-06 11:45 ` Thorsten Leemhuis
2023-07-06 16:41 ` Dave Jones
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=50f4c10d-260c-cb98-e7d2-124f5519fa68@gmail.com \
--to=bagasdotme@gmail.com \
--cc=bids.7405@bigpond.com \
--cc=davej@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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 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.