From: patchwork-bot+linux-soc@kernel.org
To: Linus Walleij <linus.walleij@linaro.org>
Cc: soc@kernel.org
Subject: Re: [PATCH] ARM: dts: ixp4xx: Add crypto engine
Date: Sat, 12 Jun 2021 16:10:16 +0000 [thread overview]
Message-ID: <162351421659.27448.13293052679685898908.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210605161007.3397216-1-linus.walleij@linaro.org>
Hello:
This patch was applied to soc/soc.git (refs/heads/for-next):
On Sat, 5 Jun 2021 18:10:07 +0200 you wrote:
> Add the crypto engine as a child of the NPE.
>
> Cc: Corentin Labbe <clabbe@baylibre.com>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ARM SoC folks: please queue this patch on top of the
> other ixp4xx changes sent by pull request.
>
> [...]
Here is the summary with links:
- ARM: dts: ixp4xx: Add crypto engine
https://git.kernel.org/soc/soc/c/e6f600e72edc
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-05 16:10 [PATCH] ARM: dts: ixp4xx: Add crypto engine Linus Walleij
2021-06-05 16:10 ` Linus Walleij
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=162351421659.27448.13293052679685898908.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=linus.walleij@linaro.org \
--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.