From: patchwork-bot+linux-soc@kernel.org
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: soc@kernel.org
Subject: Re: [GIT PULL] ARM: mvebu: dt64 for v5.19 (#1)
Date: Fri, 13 May 2022 21:40:19 +0000 [thread overview]
Message-ID: <165247801901.11200.8048784065566023472.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <87r14xr2xc.fsf@BL-laptop>
Hello:
This pull request was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Fri, 13 May 2022 15:13:19 +0200 you wrote:
> Hi,
>
> Here is the first pull request for dt64 for mvebu for v5.19.
>
> There is a conflict with the arm-soc tree and as pointed by Stephen
> Rothwell and confirmed by Krzysztof Kozlowski, the correct resolution is
> to take the commit 2f00bb4a69c7 ("arm64: dts: marvell: align SPI NOR
> node name with dtschema"), so the node name should be "flash", not
> "spi-flash".
>
> [...]
Here is the summary with links:
- [GIT,PULL] ARM: mvebu: dt64 for v5.19 (#1)
https://git.kernel.org/soc/soc/c/5aef4d1ecc97
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-05-13 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 13:13 [GIT PULL] ARM: mvebu: dt64 for v5.19 (#1) Gregory CLEMENT
2022-05-13 21:40 ` 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=165247801901.11200.8048784065566023472.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=gregory.clement@bootlin.com \
--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