All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: "Li, Steve" <Steve.Li@imaginecommunications.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: ALSA license
Date: Thu, 31 Mar 2016 10:46:52 +0900	[thread overview]
Message-ID: <56FC818C.8090601@sakamocchi.jp> (raw)
In-Reply-To: <3CD7D8096827214EA72BFDC6B95C7CC931B5654F@VEREXCH02.harrisbroadcast.com>

Hi,

On Mar 30 2016 04:06, Li, Steve wrote:
> I am trying to use ALSA in a commercial application. I see that in the introduction page, ALSA is
> licensed under GPL and LGPL. Can you tell me which part of ALSA is licensed under LGPL? What is
> the best way to find out this information?

It's just reading license information included in each software packages 
(in most cases COPYRIGHT file). Under ALSA project, several softwares 
are developed. Which softwares do you plan to use?


Regards

Takashi Sakamoto

  reply	other threads:[~2016-03-31  1:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-29 19:06 ALSA license Li, Steve
2016-03-31  1:46 ` Takashi Sakamoto [this message]
2016-03-31 14:04   ` Li, Steve
2016-03-31 14:13 ` Clemens Ladisch

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=56FC818C.8090601@sakamocchi.jp \
    --to=o-takashi@sakamocchi.jp \
    --cc=Steve.Li@imaginecommunications.com \
    --cc=alsa-devel@alsa-project.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.