linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Henry Ptasinski" <henryp@broadcom.com>
To: "dwmw2@infradead.org" <dwmw2@infradead.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"Brett Rudley" <brudley@broadcom.com>,
	"Arend Van Spriel" <arend@broadcom.com>,
	"Roland Vossen" <rvossen@broadcom.com>,
	"Henry Ptasinski" <henryp@broadcom.com>
Subject: Re: [PATCH 0/3] linux-firmware: Updated firmware and new license for brcm firmware
Date: Thu, 7 Apr 2011 14:15:21 -0700	[thread overview]
Message-ID: <20110407211521.GA3252@broadcom.com> (raw)
In-Reply-To: <1302015522-20601-1-git-send-email-henryp@broadcom.com>

On Tue, Apr 05, 2011 at 07:58:39AM -0700, Henry Ptasinski wrote:
> David,
> 
> Here's a short patch series for the linux-firmware repo, including a much
> shorter license, some file renaming to get the firmware repo in synch with the
> firmware names expected by the drivers, and a new version of firmware which
> should resolve a lot of the stability issues people are seeing with the
> brcmsmac driver.  Please apply them to the linux-firmware repo.

David,

While there was some discussion about patch #2, I believe all the concerns have
been addressed, so please apply all 3 patches to the linux-firmware repo.

Thanks,
- Henry



  parent reply	other threads:[~2011-04-07 21:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 14:58 [PATCH 0/3] linux-firmware: Updated firmware and new license for brcm firmware Henry Ptasinski
2011-04-05 14:58 ` [PATCH 2/3] linux-firmware: Removed codeversion from brcm firmware filenames Henry Ptasinski
2011-04-05 15:34   ` Larry Finger
2011-04-05 17:51     ` Henry Ptasinski
2011-04-05 19:00       ` Larry Finger
2011-04-05 19:29         ` Greg KH
2011-04-05 20:33           ` Larry Finger
2011-04-05 20:42             ` Greg KH
2011-04-05 14:58 ` [PATCH 3/3] linux-firmware: updated firmware for BCM4313, BCM43224, and BCM43225 chips Henry Ptasinski
2011-04-21 18:30   ` [PATCH 0/3] linux-firmware: brcm firmware fixes Henry Ptasinski
2011-04-21 18:30     ` [PATCH 1/3] linux-firmware: Simplified license file for brcm firmware Henry Ptasinski
2011-04-21 18:30     ` [PATCH 2/3] linux-firmware: Removed codeversion from brcm firmware filenames Henry Ptasinski
2011-04-21 18:30     ` [PATCH 3/3] linux-firmware: updated firmware for BCM4313, BCM43224, and BCM43225 chips Henry Ptasinski
2011-04-07 21:15 ` Henry Ptasinski [this message]
2011-04-08  6:41   ` [PATCH 0/3] linux-firmware: Updated firmware and new license for brcm firmware Johannes Berg
2011-04-08 14:49     ` Henry Ptasinski
2011-04-08 14:51   ` [PATCH 1/3] linux-firmware: Simplified license file " Henry Ptasinski
2011-04-08 14:51   ` [PATCH 2/3] linux-firmware: Removed codeversion from brcm firmware filenames Henry Ptasinski
2011-04-08 14:51   ` [PATCH 3/3] linux-firmware: updated firmware for BCM4313, BCM43224, and BCM43225 chips Henry Ptasinski

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=20110407211521.GA3252@broadcom.com \
    --to=henryp@broadcom.com \
    --cc=arend@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=devel@linuxdriverproject.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rvossen@broadcom.com \
    /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).