All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Mark Hounschell <markh@compro.net>
Cc: "Giedrius Statkevičius" <giedrius.statkevicius@gmail.com>,
	lidza.louina@gmail.com, devel@driverdev.osuosl.org,
	driverdev-devel@linuxdriverproject.org,
	linux-kernel@vger.kernel.org, dan.carpenter@oracle.com
Subject: Re: [PATCH v2] dgnc: Don't save boards in memory that have failed to initialize
Date: Sun, 15 Mar 2015 17:38:42 +0100	[thread overview]
Message-ID: <20150315163842.GA18616@kroah.com> (raw)
In-Reply-To: <550575ED.5020907@compro.net>

On Sun, Mar 15, 2015 at 08:07:09AM -0400, Mark Hounschell wrote:
> >>Greg, while I'm here, how can we get Digi firmware into the kernel firmware
> >>tree? The dgap card is useless without it and I suspect the dgnc is as well.
> >
> >Submit a patch to the linux-firmware git tree with the firmware in it.
> >
> 
> I don't know if the binary blobs are GPL compatable?

Look at the hundreds of different licenses in the linux-firmware tree,
they are all different for different reasons / companies.  Use whatever
license Digi uses for their firmware, it might already be part of the
tree.

hope this helps,

greg k-h

  reply	other threads:[~2015-03-15 16:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 16:29 [PATCH v2] dgnc: Don't save boards in memory that have failed to initialize Giedrius Statkevičius
2015-03-10  7:39 ` Dan Carpenter
2015-03-12 10:08 ` Greg KH
2015-03-12 10:20   ` Dan Carpenter
2015-03-12 16:14   ` Giedrius Statkevičius
2015-03-13 20:55     ` Mark Hounschell
2015-03-14  8:44       ` Greg KH
2015-03-15 12:07         ` Mark Hounschell
2015-03-15 16:38           ` Greg KH [this message]
2015-03-16 17:18           ` Mark Hounschell
2015-03-13 20:06   ` Giedrius Statkevičius

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=20150315163842.GA18616@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.carpenter@oracle.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=giedrius.statkevicius@gmail.com \
    --cc=lidza.louina@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markh@compro.net \
    /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.