From: "Michael Büsch" <m@bues.ch>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org, b43-dev@lists.infradead.org
Subject: [RFC/RFT] fwcutter: Add firmware 6.30.163.46
Date: Mon, 29 Jul 2013 19:03:39 +0200 [thread overview]
Message-ID: <20130729190339.5a84a2ca@milhouse> (raw)
In-Reply-To: <1375115025-26851-1-git-send-email-Larry.Finger@lwfinger.net>
On Mon, 29 Jul 2013 11:23:45 -0500
Larry Finger <Larry.Finger@lwfinger.net> wrote:
> Is this change worthwhile?
Why not? Doesn't hurt to have it.
> @@ -874,4 +1047,12 @@ static const struct file files[] =
> .flags = FW_FLAG_LE | FW_FLAG_V4,
> .extract = _e1b05e268bcdbfef3560c28fc161f30e,
> },
> + {
> + /* http://www.lwfinger.com/b43-firmware/broadcom-wl-6.30.163.46.tar.bz2 */
Could you also add the original URL here?
--
Michael
-------------- 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/20130729/fd165544/attachment.sig>
prev parent reply other threads:[~2013-07-29 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 16:23 [RFC/RFT] fwcutter: Add firmware 6.30.163.46 Larry Finger
2013-07-29 17:03 ` 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=20130729190339.5a84a2ca@milhouse \
--to=m@bues.ch \
--cc=Larry.Finger@lwfinger.net \
--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 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).