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.2
Date: Wed, 23 Nov 2022 12:00:24 +0000 [thread overview]
Message-ID: <166920482414.7332.7482244438717960983.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <CACPK8Xfsc8BaL_qAgV+3Rk-AFcQoDVfTpMzHvq_rR-UYqwpNNQ@mail.gmail.com>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Tue, 22 Nov 2022 00:57:29 +0000 you wrote:
> Hello soc maintainers,
>
> Here are the aspeed device tree changes for v6.2.
>
> The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
>
> Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
>
> [...]
Here is the summary with links:
- [GIT,PULL] ARM: aspeed: devicetree changes for 6.2
https://git.kernel.org/soc/soc/c/375aab101818
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:[~2022-11-23 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 0:57 [GIT PULL] ARM: aspeed: devicetree changes for 6.2 Joel Stanley
2022-11-22 0:57 ` Joel Stanley
2022-11-23 12:00 ` 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=166920482414.7332.7482244438717960983.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.