From: "Michael Büsch" <m@bues.ch>
To: b43-dev@lists.infradead.org
Subject: [PATCH] b43-fwcutter: pack correct ucode for brcmsmac fw
Date: Fri, 7 Dec 2012 19:22:39 +0100 [thread overview]
Message-ID: <20121207192239.60b857a2@milhouse> (raw)
In-Reply-To: <50C21573.3040209@hauke-m.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 07 Dec 2012 17:12:35 +0100
Hauke Mehrtens <hauke@hauke-m.de> wrote:
> Yes I thing a new release would be nice, as the wrong firmware will
> probably not work and could cause people some trouble.
ok cool. I released 017.
- --
Greetings, Michael.
PGP encryption is encouraged / 908D8B0E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJQwjPvAAoJEPUyvh2QjYsOvqgQAMTuuItRe8MIyPqgv0kohc6V
DmXSXk7N4xJWrxcxdVv4tqdeXjnW/23PxpGk629tt3+yH3C+xEFooJKmCxqfvxtm
UQF5SVENX2FAfMIrbo2vILIIx3n1YnoG/xSf8NDMNJG8dHi5dC1zc6l1x6z5I3Pl
+5ADb2yT7SgyvrMGGo6G5nL3UbdsdtDVAG+e7AmEHBFioTkGWe/MgKVLrDIKwcHR
EFjE97LC4CD/6nAiQ9WWLW5GddoflcwYkVZ6z0WDj3FJTDUq/Z+gzoQZ5YoS6P/v
nzOmQESId+ilt8bHnTUw6sHtQ4ohV1gUpd6Sr/hKchdq0GLOi9N0ZfCRxY6/CugB
wVkzji3YbRoiJpNV0xdvTONjq8XgB6agYM7syGFYWhiz2qAchDsdv2FFf1Nxz775
1xHsYd+8f1HywcHWxsC9C9okud+4WkzctddCo8Cf4XuI/pboDgyxvvuv3ZEmA8CM
MEXdtG3Qv/KP5v5xUOfTfONum/ab3R2NF5pam16Chvw1oZY/VuLNt66AdG+IvF74
fdnl0sd/OP2ErLV2gWVO2bBjat2w70ox5ot4XMB9baz3TQZgO7yTj4nj90PYm1UK
97SBGhyFbgHVQl6PmilmWzo7fGIoyr2CWjC6BGYfqyLS4RZYh0kI9W2Ldn5s+luc
eqfHKgXejlLC2v5Hb2bT
=kwMB
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2012-12-07 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-06 21:44 [PATCH] b43-fwcutter: pack correct ucode for brcmsmac fw Hauke Mehrtens
2012-12-07 13:17 ` Michael Büsch
2012-12-07 16:12 ` Hauke Mehrtens
2012-12-07 18:22 ` Michael Büsch [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=20121207192239.60b857a2@milhouse \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.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 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).