From: Krzysztof Kozlowski <krzk@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>,
Florian Fainelli <florian.fainelli@broadcom.com>
Cc: soc@kernel.org, "Rob Herring" <robh@kernel.org>,
"Gregor Herburger" <gregor.herburger@linutronix.de>,
"Maíra Canal" <mcanal@igalia.com>,
"Stefan Wahren" <wahrenst@gmx.net>,
linux-arm-kernel@lists.infradead.org,
"Kevin Hilman" <khilman@kernel.org>,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [GIT PULL 2/2] Broadcom devicetree-arm64 changes for 7.1
Date: Wed, 1 Apr 2026 16:47:39 +0200 [thread overview]
Message-ID: <3f7879d0-9e5d-4c00-a5dc-4871a049afd0@kernel.org> (raw)
In-Reply-To: <df52b2ae-4b8b-487a-bb6b-07bf021500b5@app.fastmail.com>
On 01/04/2026 16:37, Arnd Bergmann wrote:
> On Wed, Apr 1, 2026, at 14:02, Krzysztof Kozlowski wrote:
>> On 01/04/2026 13:18, Krzysztof Kozlowski wrote:
>>> On Mon, Mar 23, 2026 at 12:02:39PM -0700, Florian Fainelli wrote:
>>>
>>> I think the same issue was last time and repo is non korg, so nothing
>>> seems to improve.
>>
>>
>> Maybe last time I mentioned this only internally or on IRC, so could get
>> lost. Please get your key in to the kernel keyring, to solve above. Pull
>> is not rejected, but I leave it to Arnd who might have your key.
>>
>> How to get key signed? Obviously conferences are the easiest way, but
>> other is to find people around you or on your travel itinerary via
>> ksmap. Eventually many people do video call cross signing, so even
>> travel is not needed. I video signed twice, but that was an exception
>> because I prefer to meet in person. Kernel wiki has guideline on all
>> this, so I am not saying anything new here.
>
> I think what happened is that the key expired. I can see that
> Florian is using the same key as the last 113 times, and I see
> it has signatures from other developers, but the copy I have
> expired in 2024, which probably caused it to disappear from
> the keyservers.
>
> this is what I see:
>
> $ 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.
I don't think DSA1024 can be accepted now in keyring, so this requires a
new key, cross signed by the old one.
> FE4FA16F65261D8BDA57BCBD61579915B563760E
> uid [ expired] Florian Fainelli <f.fainelli@gmail.com>
> sig DE95E6B5B9FA86CB 2008-09-16 Florian Fainelli <florian.fainelli@openpattern.org>
> sig 9B1F67D46FF7D7AB 2008-09-16 Florian Fainelli <florian.fainelli@telecomint.eu>
> sig F91A73ED49C617B5 2008-09-16 Florian Fainelli <florian@minet.net>
> sig 972BE49811AD8F26 2008-09-16 Florian Fainelli <florian@openwrt.org>
> sig 3 61579915B563760E 2008-09-16 Florian Fainelli <f.fainelli@gmail.com>
> sig 3 61579915B563760E 2014-11-09 Florian Fainelli <f.fainelli@gmail.com>
> sig 3A8F3B2F5A7C9849 2016-03-12 Michael Turquette <mturquette@baylibre.com>
> sig E6BF0DCBA6694C84 2017-04-08 Andrew Lunn <andrew@lunn.ch>
> sig 987E58D467ED50B8 2017-04-09 [User ID not found]
>
> Arnd
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-01 14:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 19:02 [GIT PULL 1/2] Broadcom devicetree changes for 7.1 Florian Fainelli
2026-03-23 19:02 ` [GIT PULL 2/2] Broadcom devicetree-arm64 " Florian Fainelli
2026-04-01 11:18 ` Krzysztof Kozlowski
2026-04-01 12:02 ` Krzysztof Kozlowski
2026-04-01 14:37 ` Arnd Bergmann
2026-04-01 14:47 ` Krzysztof Kozlowski [this message]
2026-04-01 16:33 ` Arnd Bergmann
2026-04-01 16:38 ` Krzysztof Kozlowski
2026-04-01 16:41 ` Florian Fainelli
2026-04-01 16:49 ` Mark Brown
2026-04-01 16:50 ` Arnd Bergmann
2026-03-27 11:53 ` [GIT PULL 1/2] Broadcom devicetree " Krzysztof Kozlowski
2026-03-27 16:26 ` Florian Fainelli
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=3f7879d0-9e5d-4c00-a5dc-4871a049afd0@kernel.org \
--to=krzk@kernel.org \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=florian.fainelli@broadcom.com \
--cc=gregor.herburger@linutronix.de \
--cc=khilman@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mcanal@igalia.com \
--cc=robh@kernel.org \
--cc=soc@kernel.org \
--cc=wahrenst@gmx.net \
/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