linux-fscrypt.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Steev Klimaszewski <steev@kali.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Elliot Berman <eberman@codeaurora.org>,
	Thara Gopinath <thara.gopinath@linaro.org>,
	Satya Tangirala <satyat@google.com>,
	Alim Akhtar <alim.akhtar@samsung.com>,
	Avri Altman <avri.altman@wdc.com>,
	linux-fscrypt@vger.kernel.org, Andy Gross <agross@kernel.org>,
	John Stultz <john.stultz@linaro.org>,
	Can Guo <cang@codeaurora.org>,
	Barani Muthukumaran <bmuthuku@qti.qualcomm.com>
Subject: Re: [PATCH v6 0/5] Inline crypto support on DragonBoard 845c
Date: Tue, 21 Jul 2020 22:25:41 -0700	[thread overview]
Message-ID: <20200722052541.GB39383@sol.localdomain> (raw)
In-Reply-To: <159539205429.31352.16564389172198122676.b4-ty@oracle.com>

Hi Martin,

On Wed, Jul 22, 2020 at 12:28:29AM -0400, Martin K. Petersen wrote:
> On Fri, 10 Jul 2020 00:20:07 -0700, Eric Biggers wrote:
> 
> > This patchset implements UFS inline encryption support on the
> > DragonBoard 845c, using the Qualcomm Inline Crypto Engine (ICE)
> > that's present on the Snapdragon 845 SoC.
> > 
> > This is based on top of scsi/5.9/scsi-queue, which contains the
> > ufshcd-crypto patches by Satya Tangirala.
> > 
> > [...]
> 
> Applied to 5.9/scsi-queue, thanks!
> 
> [1/5] scsi: firmware: qcom_scm: Add support for programming inline crypto keys
>       https://git.kernel.org/mkp/scsi/c/e10d24786adb
> [2/5] scsi: ufs-qcom: Name the dev_ref_clk_ctrl registers
>       https://git.kernel.org/mkp/scsi/c/12700db4f9f7
> [4/5] scsi: ufs: Add program_key() variant op
>       https://git.kernel.org/mkp/scsi/c/a5fedfacb402
> [5/5] scsi: ufs-qcom: Add Inline Crypto Engine support
>       https://git.kernel.org/mkp/scsi/c/de9063fbd769

Seems that something went wrong when you applied patch 5.  It's supposed to add
the file ufs-qcom-ice.c, but the committed version doesn't have that file.

- Eric

  reply	other threads:[~2020-07-22  5:25 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10  7:20 [PATCH v6 0/5] Inline crypto support on DragonBoard 845c Eric Biggers
2020-07-10  7:20 ` [PATCH v6 1/5] firmware: qcom_scm: Add support for programming inline crypto keys Eric Biggers
2020-07-10  7:20 ` [PATCH v6 2/5] scsi: ufs-qcom: name the dev_ref_clk_ctrl registers Eric Biggers
2020-07-12  8:42   ` Avri Altman
2020-07-22  5:07   ` Bjorn Andersson
2020-07-10  7:20 ` [PATCH v6 3/5] arm64: dts: sdm845: add Inline Crypto Engine registers and clock Eric Biggers
2020-07-14 14:16   ` Martin K. Petersen
2020-07-14 16:15     ` Eric Biggers
2020-07-14 16:35       ` Rob Herring
2020-07-14 16:43         ` Eric Biggers
2020-07-14 16:46           ` Martin K. Petersen
2020-07-14 16:59           ` Rob Herring
2020-07-14 17:12             ` Eric Biggers
2020-07-14 17:31               ` Bjorn Andersson
2020-07-14 17:43                 ` Bjorn Andersson
2020-07-14 17:57                   ` Eric Biggers
2020-07-14 20:00                     ` Bjorn Andersson
2020-07-15  3:00                       ` Eric Biggers
2020-07-20 17:07                         ` Eric Biggers
2020-07-21 18:20                           ` Eric Biggers
2020-07-22  5:11                           ` Bjorn Andersson
2020-07-14 17:36               ` Rob Herring
2020-07-10  7:20 ` [PATCH v6 4/5] scsi: ufs: add program_key() variant op Eric Biggers
2020-07-12  9:41   ` Avri Altman
2020-07-10  7:20 ` [PATCH v6 5/5] scsi: ufs-qcom: add Inline Crypto Engine support Eric Biggers
2020-07-12  9:43   ` Avri Altman
2020-07-22  5:09   ` Bjorn Andersson
2020-07-22  4:28 ` [PATCH v6 0/5] Inline crypto support on DragonBoard 845c Martin K. Petersen
2020-07-22  5:25   ` Eric Biggers [this message]
2020-07-22 12:21     ` Martin K. Petersen

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=20200722052541.GB39383@sol.localdomain \
    --to=ebiggers@kernel.org \
    --cc=agross@kernel.org \
    --cc=alim.akhtar@samsung.com \
    --cc=avri.altman@wdc.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=bmuthuku@qti.qualcomm.com \
    --cc=cang@codeaurora.org \
    --cc=eberman@codeaurora.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-fscrypt@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=satyat@google.com \
    --cc=steev@kali.org \
    --cc=thara.gopinath@linaro.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;
as well as URLs for NNTP newsgroup(s).