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 5.14
Date: Sat, 12 Jun 2021 16:10:16 +0000 [thread overview]
Message-ID: <162351421683.27448.4703516399340434858.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <CACPK8XduV9F=piu1qh56g+YNOZOBYTW7b2Y=XVYafpYDwWmDYA@mail.gmail.com>
Hello:
This pull request was applied to soc/soc.git (refs/heads/for-next):
On Tue, 8 Jun 2021 02:31:19 +0000 you wrote:
> Hello Soc maintainers,
>
> A normal looking Aspeed pull request for the next merge window.
>
> The following changes since commit 6efb943b8616ec53a5e444193dccf1af9ad627b5:
>
> Linux 5.13-rc1 (2021-05-09 14:17:44 -0700)
>
> [...]
Here is the summary with links:
- [GIT,PULL] ARM: aspeed: devicetree changes for 5.14
https://git.kernel.org/soc/soc/c/131dc51df2af
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:[~2021-06-12 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 2:31 [GIT PULL] ARM: aspeed: devicetree changes for 5.14 Joel Stanley
2021-06-08 2:31 ` Joel Stanley
2021-06-12 16:10 ` 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=162351421683.27448.4703516399340434858.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.