All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Henry Ptasinski <henryp@broadcom.com>,
	David Woodhouse <dwmw2@infradead.org>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	Brett Rudley <brudley@broadcom.com>,
	"grundler@google.com" <grundler@google.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	rvossen@broadcom.com, dowan@broadcom.com, arend@broadcom.com
Subject: Re: [PATCH v2] linux-firmware: brcm: Removed codeversion from firmware filenames.
Date: Wed, 8 Dec 2010 14:23:49 -0800	[thread overview]
Message-ID: <20101208222349.GA31641@kroah.com> (raw)
In-Reply-To: <AANLkTin70oBFYq8LMJYw6zc7oVF9-UXv=nn_ophx+L2S@mail.gmail.com>

On Wed, Dec 08, 2010 at 11:07:53PM +0100, Rafał Miłecki wrote:
> 2010/12/8 Henry Ptasinski <henryp@broadcom.com>:
> > Second attempt at cleaning up firmware filenames.
> >
> > The basename-apiversion-codeversion construction for firmware filenames is not
> > used by most other firmware files, adds complexity, and is not providing any
> > value.  Renamed the firmware files using just basename-apiversion.  Also, fixed
> > WHENCE to have correct path to brcmfmac files.
> >
> > Signed-off-by: Henry Ptasinski <henryp@broadcom.com>
> 
> Henry, I believe we got report that Red Hat can not include your
> firmware anyway because of licensing. Can you change license to some
> common one which allows providing your firmware with distributions?

That's news to me, what specific licensing issue have you heard about
here?  Last I saw, the issues were resolved and everyone could
redistribute this firmware.

Do you have a bugzilla number?

thanks,

greg k-h

  reply	other threads:[~2010-12-08 22:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4CBE23F4.4020104@broadcom.com>
     [not found] ` <20101019233520.GA12510@kroah.com>
     [not found]   ` <FD96C117992C584DBC47231B1EB6F5568206D859DC@SJEXCHCCR02.corp.ad.broadcom.com>
     [not found]     ` <20101020004743.GB31965@kroah.com>
     [not found]       ` <20101020005546.GL10832@broadcom.com>
     [not found]         ` <20101020010320.GA370@kroah.com>
2010-10-20  2:18           ` [PATCH] staging:brcm80211:brcmfmac:change firmware/config file name Henry Ptasinski
2010-10-20  3:10             ` Greg KH
2010-10-20 11:49             ` Rafał Miłecki
2010-10-20 18:04           ` Henry Ptasinski (local)
2010-10-21 17:08           ` [PATCH] linux-firmware: brcm: Removed codeversion from firmware filenames Henry Ptasinski
2010-11-01 14:28             ` David Woodhouse
2010-12-08 20:50               ` [PATCH v2] " Henry Ptasinski
2010-12-08 22:07                 ` Rafał Miłecki
2010-12-08 22:23                   ` Greg KH [this message]
2010-12-08 23:35                     ` Henry Ptasinski
2010-12-09  0:28                       ` Rafał Miłecki
2010-12-09  1:30                         ` Henry Ptasinski
2010-12-09  9:01                           ` Rafał Miłecki
2010-10-21 17:10           ` Subject: [PATCH] staging: brcm80211: brcmfmac: " Henry Ptasinski
2010-10-21 18:26             ` Greg KH
2010-10-21 18:37               ` Subject: [PATCH v2] " 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=20101208222349.GA31641@kroah.com \
    --to=greg@kroah.com \
    --cc=arend@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=devel@linuxdriverproject.org \
    --cc=dowan@broadcom.com \
    --cc=dwmw2@infradead.org \
    --cc=grundler@google.com \
    --cc=henryp@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rvossen@broadcom.com \
    --cc=zajec5@gmail.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 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.