[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZYWvNxpLPUGCGElA@matsya>
Date: Fri, 22 Dec 2023 21:15:59 +0530
From: Vinod Koul <vkoul@...nel.org>
To: "Mukunda,Vijendar" <vijendar.mukunda@....com>
Cc: broonie@...nel.org, alsa-devel@...a-project.org,
Basavaraj.Hiregoudar@....com, Sunil-kumar.Dommati@....com,
pierre-louis.bossart@...ux.intel.com, vinod.koul@...el.com,
venkataprasad.potturu@....com,
Bard Liao <yung-chuan.liao@...ux.intel.com>,
Sanyog Kale <sanyog.r.kale@...el.com>,
open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 04/12] drivers: soundwire: refactor soundwire pads enable
On 22-12-23, 16:04, Mukunda,Vijendar wrote:
> On 22/12/23 14:51, Vinod Koul wrote:
> > 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
> Will push the license update patch first.
> >
> > Btw why would you want to do the change of license form GPL to dual?
> As this code being used by AMD SOF stack which uses dual license,
> So we want to maintain the same license terms.
SOF is firmware, do you share this kernel code with sofproject, that
doesnt make sense to me, maybe I am missing something
--
~Vinod
Powered by blists - more mailing lists