From: "Rafał Miłecki" <zajec5@gmail.com>
To: Florian Fainelli <florian.fainelli@broadcom.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Hauke Mehrtens <hauke@hauke-m.de>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH 1/2] ARM: dts: BCM5301X: Relicense Hauke's code to the GPL 2.0+ / MIT
Date: Fri, 19 May 2023 07:18:14 +0200 [thread overview]
Message-ID: <aaf324b7-2e83-e82d-5f88-b11e24cd375a@gmail.com> (raw)
In-Reply-To: <647ab902-a851-bd15-958f-8a25244c2dcf@broadcom.com>
On 19.05.2023 01:00, Florian Fainelli wrote:
> On 5/15/23 08:19, Rafał Miłecki wrote:
>> From: Rafał Miłecki <rafal@milecki.pl>
>>
>> Move code added by Hauke to the bcm-ns.dtsi which uses dual licensing.
>> That syncs more Northstar code to be based on the same licensing schema.
>>
>> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
>> Cc: Hauke Mehrtens <hauke@hauke-m.de>
>> ---
>
> Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
Please don't / revert until we get Acked-by from Hauke.
I'm sorry I didn't make that clear.
next prev parent reply other threads:[~2023-05-19 5:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 15:19 [PATCH 1/2] ARM: dts: BCM5301X: Relicense Hauke's code to the GPL 2.0+ / MIT Rafał Miłecki
2023-05-15 15:19 ` [PATCH 2/2] ARM: dts: BCM5301X: Relicense AXI interrupts " Rafał Miłecki
2023-05-18 22:59 ` Florian Fainelli
2023-05-20 9:09 ` Hauke Mehrtens
2023-05-18 23:00 ` [PATCH 1/2] ARM: dts: BCM5301X: Relicense Hauke's " Florian Fainelli
2023-05-19 5:18 ` Rafał Miłecki [this message]
2023-05-23 16:30 ` Florian Fainelli
2023-05-20 9:09 ` Hauke Mehrtens
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=aaf324b7-2e83-e82d-5f88-b11e24cd375a@gmail.com \
--to=zajec5@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rafal@milecki.pl \
--cc=robh+dt@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).