From: patchwork-bot+linux-soc@kernel.org
To: Joel Stanley <joel@jms.id.au>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] ARM: aspeed: devicetree changes for 6.7
Date: Mon, 16 Oct 2023 21:31:57 +0000 [thread overview]
Message-ID: <169749191772.22284.6961066707017660050.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <CACPK8XebMAQvgQTRH+KoaTFg7CzRkS79Fz3Kn8p4mbaezWGkUQ@mail.gmail.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Mon, 16 Oct 2023 12:17:46 +1030 you wrote:
> Hello soc maintainers,
>
> I've rejigged my gpg setup and I'm now signing with a new sub-key. Let
> me know if that causes any issues.
>
> The following changes since commit 0bb80ecc33a8fb5a682236443c1e740d5c917d1d:
>
> [...]
Here is the summary with links:
- [GIT,PULL] ARM: aspeed: devicetree changes for 6.7
https://git.kernel.org/soc/soc/c/94d310e17858
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-16 21:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-16 1:47 [GIT PULL] ARM: aspeed: devicetree changes for 6.7 Joel Stanley
2023-10-16 21:31 ` patchwork-bot+linux-soc [this message]
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=169749191772.22284.6961066707017660050.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=joel@jms.id.au \
--cc=soc@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