From: "Michael Büsch" <m@bues.ch>
To: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: b43-fwcutter release 020
Date: Fri, 22 May 2026 19:26:35 +0200 [thread overview]
Message-ID: <20260522192635.6fa6f7e1@barney> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 377 bytes --]
b43-fwcutter - Firmware extraction tool for b43 wireless
It's been quite a while since the last release and a couple of changes have piled up.
The release consists mainly of some new extraction lists (thanks to all contributors!)
and compiler warning fixes.
https://github.com/mbuesch/b43-tools/releases/tag/b43-fwcutter-020
--
Michael Büsch
https://bues.ch/
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
b43-dev mailing list
b43-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/b43-dev
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Büsch" <m@bues.ch>
To: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org
Subject: b43-fwcutter release 020
Date: Fri, 22 May 2026 19:26:35 +0200 [thread overview]
Message-ID: <20260522192635.6fa6f7e1@barney> (raw)
[-- Attachment #1: Type: text/plain, Size: 377 bytes --]
b43-fwcutter - Firmware extraction tool for b43 wireless
It's been quite a while since the last release and a couple of changes have piled up.
The release consists mainly of some new extraction lists (thanks to all contributors!)
and compiler warning fixes.
https://github.com/mbuesch/b43-tools/releases/tag/b43-fwcutter-020
--
Michael Büsch
https://bues.ch/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2026-05-22 17:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 17:26 Michael Büsch [this message]
2026-05-22 17:26 ` b43-fwcutter release 020 Michael Büsch
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=20260522192635.6fa6f7e1@barney \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.org \
--cc=linux-wireless@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.