From: Jakob Haufe <sur5r@debian.org>
To: Salvatore Bonaccorso <carnil@debian.org>
Cc: 833035@bugs.debian.org, Chris Rhodin <chris@notav8.com>,
ben@decadent.org.uk, Johan Hovold <johan@kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware
Date: Fri, 11 Nov 2022 19:14:11 +0100 [thread overview]
Message-ID: <20221111191411.0cc26c1d@beer> (raw)
In-Reply-To: <Y25mYI9tLSRJ7bbS@eldamar.lan>
[-- Attachment #1: Type: text/plain, Size: 663 bytes --]
On Fri, 11 Nov 2022 16:12:32 +0100
Salvatore Bonaccorso <carnil@debian.org> wrote:
> Jakob, were you able to forward the patch upstream? I'm including
> Johan and linux-usb list in this reply now.
No, I originally wanted to understand the differences of the firmware
loading mechanism as I assumed a patch migrating away from the unified
firmware interface would not be accepted anyway.
Unfortunately, I never found time to do this.
Thanks for bringing this up again.
Given I have two different affected devices, I am more than happy to
test any new versions of this patch.
Cheers,
sur5r
--
ceterum censeo microsoftem esse delendam.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2022-11-11 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220207153349.67de08dc@beer.h47.haufe.it>
[not found] ` <20160731071614.13615.81977.reportbug@proliant.robinstreet>
[not found] ` <YgIVt0i6zxGJFNDT@eldamar.lan>
2022-11-11 15:12 ` Bug#833035: linux-image-3.16.0-4-amd64: Keyspan USB serial adapter USA-49WLC failed to load firmware Salvatore Bonaccorso
2022-11-11 18:14 ` Jakob Haufe [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=20221111191411.0cc26c1d@beer \
--to=sur5r@debian.org \
--cc=833035@bugs.debian.org \
--cc=ben@decadent.org.uk \
--cc=carnil@debian.org \
--cc=chris@notav8.com \
--cc=johan@kernel.org \
--cc=linux-usb@vger.kernel.org \
/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.