From: "Arnd Bergmann" <arnd@arndb.de>
To: "Krzysztof Kozlowski" <krzk@kernel.org>,
"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, 01 Apr 2026 18:33:41 +0200 [thread overview]
Message-ID: <83a52edc-1d46-4eaf-996e-924ed3a00c83@app.fastmail.com> (raw)
In-Reply-To: <3f7879d0-9e5d-4c00-a5dc-4871a049afd0@kernel.org>
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,
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.
> I don't think DSA1024 can be accepted now in keyring, so this requires a
> new key, cross signed by the old one.
+1
Arnd
next prev parent reply other threads:[~2026-04-01 16:34 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
2026-04-01 16:33 ` Arnd Bergmann [this message]
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=83a52edc-1d46-4eaf-996e-924ed3a00c83@app.fastmail.com \
--to=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=krzk@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