Re: [GIT PULL 2/2] Broadcom devicetree-arm64 changes for 7.1

[Florian Fainelli <florian.fainelli@broadcom.com>]

On 4/1/26 09:38, Krzysztof Kozlowski wrote:
> On 01/04/2026 18:33, Arnd Bergmann wrote:
>> On Wed, Apr 1, 2026, at 16:47, Krzysztof Kozlowski wrote:
>>> On 01/04/2026 16:37, Arnd Bergmann wrote:
>>>> $ gpg --list-sigs 9BE46ADFE60625D891F72B8587D0969C44070704
>>>> pub   dsa1024/61579915B563760E 2008-09-16 [SCA] [expired: 2024-11-06]
>>>
>>> dsa1024 might be another answer... DSA1024 was deprecated by NIST in
>>> 2013, so maybe gnugp even drops it just like keys with too weak signatures?
>>>
>>> But another problem is that I do not see it in the `git log` of keyring
>>> at all which suggests it wasn't ever submitted.
>>
>> Indeed, that also explains why the Broadcom tree is hosted on github
>> rather than git.kernel.org. While using the kernel.org hosting
>> is by no means a requirement, github does occasionally cause problems,
> 
> Kind of, but quoting Linus' policy - either kernel.org or properly
> signed pulls by a key in the keyring.
> 
> Of course new SoCs/maintainers are exempted of that rule, but this does
> not apply here.
> 
>> and I do get a bit annoyed when it takes ages to pull from that.
>>
>> Florian, I don't know if there is a Broadcom specific policy that
>> requires you to use the corporate github account, but if you
>> are setting up a new key already, it may be a good time to
>> also move the hosting.

OK, I will get going with moving the hosting to kernel.org. What about 
this specific pull request, will it go through or is relocating the 
hosting mandatory for it to be accepted?
-- 
Florian