[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OS3PR01MB8460AA34CBDD0C2BBE6F2399C2A89@OS3PR01MB8460.jpnprd01.prod.outlook.com>
Date: Fri, 24 Feb 2023 15:03:35 +0000
From: DLG Adam Ward <DLG-Adam.Ward.opensource@...renesas.com>
To: Nick Alcock <nick.alcock@...cle.com>, Lee Jones <lee@...nel.org>
CC: DLG Adam Ward <DLG-Adam.Ward.opensource@...renesas.com>,
"mcgrof@...nel.org" <mcgrof@...nel.org>,
"linux-modules@...r.kernel.org" <linux-modules@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Hitomi Hasegawa <hasegawa-hitomi@...itsu.com>,
Support Opensource <support.opensource@...semi.com>
Subject: RE: [PATCH 18/27] kbuild, mfd: remove MODULE_LICENSE in non-modules
On 23/02/2023 19:25, Nick Alcock wrote:
>> Makes sense - but if you need to do a V2, would you mind removing the erroneous claim on DA9055 at the same time?
>I don't know what this means. There are two references to DA9055 in this patch, both in context (not in modified lines), one in drivers/mfd/da9055-core.c, the other in rivers/mfd/da9055-i2c.c. To me these both seem likely to be DA9055-related. Are you saying that one of them isn't?
The comment was followed by this link - https://elixir.bootlin.com/linux/latest/source/drivers/mfd/Kconfig#L36
This files talks about the driver being a module, but, as you correctly point out, it is not.
And never has been.
So it is worth removing.
Powered by blists - more mailing lists