From: Eric Biggers <ebiggers@kernel.org>
To: Peng Zhou <peng.zhou@mediatek.com>
Cc: linux-mmc@vger.kernel.org,
Chaotian Jing <chaotian.jing@mediatek.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Satya Tangirala <satyat@google.com>,
devicetree@vger.kernel.org,
Adrian Hunter <adrian.hunter@intel.com>,
Wulin Li <wulin.li@mediatek.com>,
Mason Zhang <mason.zhang@mediatek.com>
Subject: Re: [PATCH v2 0/4] MediaTek eMMC inline encryption support
Date: Mon, 8 Mar 2021 15:02:19 -0800 [thread overview]
Message-ID: <YEas+9mY5zdJh6mX@gmail.com> (raw)
In-Reply-To: <20210308080855.30459-1-peng.zhou@mediatek.com>
On Mon, Mar 08, 2021 at 04:08:56PM +0800, Peng Zhou wrote:
> Hello,
>
> Mediatek eMMC hardware IP has Inline Crypto Engine (ICE),
> we support inline encryption now.
>
> For Inline Crypto Engine (ICE), see:
> - https://lore.kernel.org/linux-arm-msm/20210126001456.382989-2-ebiggers@kernel.org/T/
>
> Changed in v2:
> - fix email format
> - change some description
>
> Peng Zhou (4):
> mmc: Mediatek: add Inline Crypto Engine support
> mmc: Mediatek: enable crypto hardware engine
> arm64: dts: Mediatek: MT6779: add mmc node with ICE setting
> dt-bingdings: mmc: Mediatek: add ICE clock
>
> .../devicetree/bindings/mmc/mtk-sd.yaml | 6 ++-
> arch/arm64/boot/dts/mediatek/mt6779.dtsi | 14 +++++++
> drivers/mmc/host/mtk-sd.c | 42 ++++++++++++++++++-
> 3 files changed, 59 insertions(+), 3 deletions(-)
Now I received this cover letter 5 more times, but none of the other patches.
How are you sending this out?
- Eric
next parent reply other threads:[~2021-03-08 23:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210308080855.30459-1-peng.zhou@mediatek.com>
2021-03-08 23:02 ` Eric Biggers [this message]
2021-03-09 1:53 [PATCH v2 0/4] MediaTek eMMC inline encryption support Peng Zhou
-- strict thread matches above, loose matches on Subject: below --
2021-03-09 1:42 Peng Zhou
2021-03-08 8:33 Mason Zhang
2021-03-08 7:39 Mason Zhang
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=YEas+9mY5zdJh6mX@gmail.com \
--to=ebiggers@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=chaotian.jing@mediatek.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=mason.zhang@mediatek.com \
--cc=peng.zhou@mediatek.com \
--cc=satyat@google.com \
--cc=ulf.hansson@linaro.org \
--cc=wulin.li@mediatek.com \
/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.