From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: <broonie@kernel.org>, <pierre-louis.bossart@linux.intel.com>,
<u.kleine-koenig@pengutronix.de>
Cc: <alsa-devel@alsa-project.org>, <patches@opensource.cirrus.com>
Subject: Re: [PATCH] ASoC: cs35l45: Relicense to GPL only
Date: Wed, 24 May 2023 09:05:56 +0000 [thread overview]
Message-ID: <20230524090556.GC68926@ediswmail.ad.cirrus.com> (raw)
In-Reply-To: <20230510092534.3919120-1-ckeepax@opensource.cirrus.com>
On Wed, May 10, 2023 at 10:25:34AM +0100, Charles Keepax wrote:
> Cirrus never intended to upstream dual licensed code, convert to
> GPL only.
>
> Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
> ---
>
> Apologies for this but this was never our intention and I believe that
> it can be a little legally involved maintaining dual licensed kernel code.
> Fortunately not that many people outside of Cirrus have contributed to
> the files in question. I have CCed everyone who has contributed both
> internally and externally.
Pierre, Uwe,
Apologies for chasing but it would be really helpful to get an
ack for this one, we need the approval of everyone who
contributed to fix the licensing issue.
Thanks,
Charles
next prev parent reply other threads:[~2023-05-24 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-10 9:25 [PATCH] ASoC: cs35l45: Relicense to GPL only Charles Keepax
2023-05-10 9:39 ` Richard Fitzgerald
2023-05-10 14:54 ` Vlad Karpovich
2023-05-24 9:05 ` Charles Keepax [this message]
2023-05-24 12:35 ` Uwe Kleine-König
2023-05-24 16:19 ` Pierre-Louis Bossart
2023-05-25 14:57 ` Mark Brown
-- strict thread matches above, loose matches on Subject: below --
2023-05-15 15:34 James Schulman
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=20230524090556.GC68926@ediswmail.ad.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=u.kleine-koenig@pengutronix.de \
/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