From: "Michael Büsch" <m@bues.ch>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
brcm80211-dev-list@broadcom.com
Subject: [RFC] b43-fwcutter: Add support for generating a fw for brcmsmac
Date: Mon, 24 Sep 2012 23:09:28 +0200 [thread overview]
Message-ID: <20120924230928.4c2fa4c2@milhouse> (raw)
In-Reply-To: <1348425562-30730-1-git-send-email-hauke@hauke-m.de>
I applied this to the git repository and released b43-fwcutter-016.
There are no other changes since 015.
--
Greetings, Michael.
PGP encryption is encouraged / 908D8B0E
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/b43-dev/attachments/20120924/aa2ccf14/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: "Michael Büsch" <m@bues.ch>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: b43-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
brcm80211-dev-list@broadcom.com
Subject: Re: [RFC] b43-fwcutter: Add support for generating a fw for brcmsmac
Date: Mon, 24 Sep 2012 23:09:28 +0200 [thread overview]
Message-ID: <20120924230928.4c2fa4c2@milhouse> (raw)
In-Reply-To: <1348425562-30730-1-git-send-email-hauke@hauke-m.de>
[-- Attachment #1: Type: text/plain, Size: 179 bytes --]
I applied this to the git repository and released b43-fwcutter-016.
There are no other changes since 015.
--
Greetings, Michael.
PGP encryption is encouraged / 908D8B0E
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-09-24 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-23 18:39 [RFC] b43-fwcutter: Add support for generating a fw for brcmsmac Hauke Mehrtens
2012-09-23 19:39 ` Michael Büsch
2012-09-23 19:39 ` Michael Büsch
2012-09-24 21:09 ` Michael Büsch [this message]
2012-09-24 21:09 ` 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=20120924230928.4c2fa4c2@milhouse \
--to=m@bues.ch \
--cc=b43-dev@lists.infradead.org \
--cc=brcm80211-dev-list@broadcom.com \
--cc=hauke@hauke-m.de \
--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.