From: Vinod Koul <vkoul@kernel.org>
To: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
Cc: broonie@kernel.org, alsa-devel@alsa-project.org,
Basavaraj.Hiregoudar@amd.com, Sunil-kumar.Dommati@amd.com,
pierre-louis.bossart@linux.intel.com, vinod.koul@intel.com,
venkataprasad.potturu@amd.com,
Bard Liao <yung-chuan.liao@linux.intel.com>,
Sanyog Kale <sanyog.r.kale@intel.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 04/12] drivers: soundwire: refactor soundwire pads enable
Date: Fri, 22 Dec 2023 14:51:19 +0530 [thread overview]
Message-ID: <ZYVVD2mL5kAePXDE@matsya> (raw)
In-Reply-To: <6d98c43d-fb90-4cfa-a22e-8fd6d5a6eb50@amd.com>
On 22-12-23, 12:45, Mukunda,Vijendar wrote:
> On 21/12/23 22:08, Vinod Koul wrote:
> > so the code is copied from a GPL declared file to now and GPL + BSD one!
> > Have you had lawyers look into this... why change one file license ?
> As per recommendations from our legal team, we have updated the license as dual
> one for amd_init.c file.
> We have also observed that license terms should be updated for other files as
> well (amd_manager.c, amd_manager.h & sdw_amd.h) as dual one, which we have
> planned to submit as a supplement patch.
Lets change that first before we move code from one license file to
another
Btw why would you want to do the change of license form GPL to dual?
--
~Vinod
next prev parent reply other threads:[~2023-12-22 9:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20231221073558.3181911-1-Vijendar.Mukunda@amd.com>
2023-12-21 7:35 ` [PATCH 01/12] ASoC/soundwire: implement generic api for scanning amd soundwire controller Vijendar Mukunda
2023-12-21 7:35 ` [PATCH 02/12] drivers: soundwire: refactor amd soundwire manager device node creation Vijendar Mukunda
2023-12-21 16:34 ` Vinod Koul
2023-12-22 5:32 ` Mukunda,Vijendar
2023-12-21 7:35 ` [PATCH 03/12] drivers: soundwire: implement function to extract slave information Vijendar Mukunda
2023-12-21 7:35 ` [PATCH 04/12] drivers: soundwire: refactor soundwire pads enable Vijendar Mukunda
2023-12-21 16:38 ` Vinod Koul
2023-12-22 7:15 ` Mukunda,Vijendar
2023-12-22 9:21 ` Vinod Koul [this message]
2023-12-22 10:34 ` Mukunda,Vijendar
2023-12-22 15:45 ` Vinod Koul
2023-12-23 2:04 ` Mukunda,Vijendar
2023-12-21 7:35 ` [PATCH 05/12] drivers: soundwire: refactor register mask structure Vijendar Mukunda
2023-12-21 7:35 ` [PATCH 06/12] ASoC: SOF: amd: add code for invoking soundwire manager helper functions Vijendar Mukunda
2023-12-21 7:35 ` [PATCH 07/12] ASoC: SOF: amd: add interrupt handling for SoundWire manager devices Vijendar Mukunda
2023-12-21 7:35 ` [PATCH 08/12] ASoC: SOF: amd: Add Soundwire DAI configuration support for AMD platforms Vijendar Mukunda
2023-12-21 7:35 ` [PATCH 09/12] ASoC: SOF: amd: add machine select logic for soundwire based platforms Vijendar Mukunda
2023-12-21 7:35 ` [PATCH 10/12] ASoC: SOF: amd: update descriptor fields for acp6.3 based platform Vijendar Mukunda
2023-12-21 7:35 ` [PATCH 11/12] ASoC: SOF: amd: select soundwire dependency flag " Vijendar Mukunda
2023-12-21 7:35 ` [PATCH 12/12] ASoC: SOF: amd: refactor acp driver pm ops Vijendar Mukunda
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=ZYVVD2mL5kAePXDE@matsya \
--to=vkoul@kernel.org \
--cc=Basavaraj.Hiregoudar@amd.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=sanyog.r.kale@intel.com \
--cc=venkataprasad.potturu@amd.com \
--cc=vijendar.mukunda@amd.com \
--cc=vinod.koul@intel.com \
--cc=yung-chuan.liao@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox