From: Krzysztof Kozlowski <krzk@kernel.org>
To: 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, arnd@arndb.de,
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 14:02:43 +0200 [thread overview]
Message-ID: <2e47f487-da04-411d-bf78-4c76ac793a91@kernel.org> (raw)
In-Reply-To: <20260401-rapid-lyrebird-of-emphasis-da7b13@quoll>
On 01/04/2026 13:18, Krzysztof Kozlowski wrote:
> On Mon, Mar 23, 2026 at 12:02:39PM -0700, Florian Fainelli wrote:
>> The following changes since commit 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f:
>>
>> Linux 7.0-rc1 (2026-02-22 13:18:59 -0800)
>>
>> are available in the Git repository at:
>>
>> https://github.com/Broadcom/stblinux.git tags/arm-soc/for-7.1/devicetree-arm64
>>
>> for you to fetch changes up to 0acb1de2b4df426a62dba33bcd80f3939636f97b:
>>
>> arm64: dts: broadcom: bcm2712: Move non simple-bus nodes to root level (2026-03-20 10:17:30 -0700)
>
> Patches were good, I wanted to merge them, but then merge complained:
>
> Can't check signature: No public key
>
> I refreshed now my keyring with kernel.org and the same.
>
> 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.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-04-01 12:35 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 [this message]
2026-04-01 14:37 ` Arnd Bergmann
2026-04-01 14:47 ` Krzysztof Kozlowski
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=2e47f487-da04-411d-bf78-4c76ac793a91@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