From: patchwork-bot+linux-soc@kernel.org
To: Heiko Stuebner <heiko@sntech.de>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] Rockchip dts32 changes for 6.3 #1
Date: Fri, 03 Feb 2023 14:30:44 +0000 [thread overview]
Message-ID: <167543464477.16250.3101597394574087180.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <5651506.31r3eYUQgx@phil>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Thu, 02 Feb 2023 00:04:52 +0100 you wrote:
> The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:
>
> Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git tags/v6.3-rockchip-dts32-1
>
> [...]
Here is the summary with links:
- [GIT,PULL] Rockchip dts32 changes for 6.3 #1
https://git.kernel.org/soc/soc/c/eacef7cc523a
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-02-03 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 23:04 [GIT PULL] Rockchip dts32 changes for 6.3 #1 Heiko Stuebner
2023-02-03 14:30 ` 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=167543464477.16250.3101597394574087180.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=heiko@sntech.de \
--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