Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Avri Altman <avri.altman@wdc.com>
Cc: linux-scsi@vger.kernel.org,
	Barani Muthukumaran <bmuthuku@qti.qualcomm.com>,
	Kuohong Wang <kuohong.wang@mediatek.com>,
	Kim Boojin <boojin.kim@samsung.com>,
	Satya Tangirala <satyat@google.com>
Subject: Re: [PATCH v2 0/3] Inline Encryption support for UFS
Date: Fri, 19 Jun 2020 23:17:49 -0400	[thread overview]
Message-ID: <yq1a70yh1f3.fsf@ca-mkp.ca.oracle.com> (raw)
In-Reply-To: <20200618024736.97207-1-satyat@google.com> (Satya Tangirala's message of "Thu, 18 Jun 2020 02:47:33 +0000")


Avri,

> This patch series adds support for inline encryption to UFS using
> the inline encryption support in the block layer. It follows the JEDEC
> UFSHCI v2.1 specification, which defines inline encryption for UFS.

I'd appreciate it if you could review this series.

Thanks!

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2020-06-20  3:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18  2:47 [PATCH v2 0/3] Inline Encryption support for UFS Satya Tangirala
2020-06-18  2:47 ` [PATCH v2 1/3] scsi: ufs: UFS driver v2.1 spec crypto additions Satya Tangirala
2020-06-18  2:47 ` [PATCH v2 2/3] scsi: ufs: UFS crypto API Satya Tangirala
2020-06-18  2:47 ` [PATCH v2 3/3] scsi: ufs: Add inline encryption support to UFS Satya Tangirala
2020-06-23 10:57   ` Alim Akhtar
2020-06-20  3:17 ` Martin K. Petersen [this message]
2020-06-20  8:28   ` [PATCH v2 0/3] Inline Encryption support for UFS Avri Altman
2020-06-21 12:35   ` Avri Altman
2020-06-21 12:47     ` Avri Altman
2020-06-21 17:46       ` Eric Biggers
2020-06-21 17:54     ` Alim Akhtar
2020-06-21 19:26       ` Eric Biggers
2020-06-22  7:09         ` Avri Altman
2020-06-21 18:24     ` Satya Tangirala
2020-06-21 18:49       ` Eric Biggers
2020-06-22  7:34 ` [PATCH v2 3/3] scsi: ufs: Add inline encryption support to UFS Avri Altman

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=yq1a70yh1f3.fsf@ca-mkp.ca.oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=avri.altman@wdc.com \
    --cc=bmuthuku@qti.qualcomm.com \
    --cc=boojin.kim@samsung.com \
    --cc=kuohong.wang@mediatek.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=satyat@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox