From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Charles Keepax <ckeepax@opensource.cirrus.com>,
broonie@kernel.org, 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 11:19:26 -0500 [thread overview]
Message-ID: <734986f7-18be-7392-17ec-cf64bf0f7b34@linux.intel.com> (raw)
In-Reply-To: <20230524090556.GC68926@ediswmail.ad.cirrus.com>
On 5/24/23 04:05, Charles Keepax wrote:
> 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.
Sorry, I missed that you were asking me...
My only contribution is a two-character change in a header file to make
cppcheck happy.
-int cs35l45_apply_patch(struct cs35l45_private *cs43l45);
+int cs35l45_apply_patch(struct cs35l45_private *cs35l45);
I double-checked with Intel legal to be sure, and there's no issue with
removing the BSD3 license.
Acked-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
next prev parent reply other threads:[~2023-05-24 16:30 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
2023-05-24 12:35 ` Uwe Kleine-König
2023-05-24 16:19 ` Pierre-Louis Bossart [this message]
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=734986f7-18be-7392-17ec-cf64bf0f7b34@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=patches@opensource.cirrus.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