OP-TEE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shyam Saini <shyamsaini@linux.microsoft.com>
To: op-tee@lists.trustedfirmware.org
Subject: Re: [RFC, PATCH 1/1] rpmb: add Replay Protected Memory Block (RPMB) driver
Date: Wed, 26 Jul 2023 20:10:16 +0000	[thread overview]
Message-ID: <e727c5c9-58c1-5d14-99c1-5d9a62998b5@linux.microsoft.com> (raw)
In-Reply-To: <233853ab-235b-d4dd-cd69-588d1a83ce4f@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]



Hi Randy,

Thank you for the reviews.

> Hi--
>
> On 7/21/23 18:40, Shyam Saini wrote:
>> diff --git a/drivers/rpmb/Kconfig b/drivers/rpmb/Kconfig
>> new file mode 100644
>> index 000000000000..f2a9ebdc4435
>> --- /dev/null
>> +++ b/drivers/rpmb/Kconfig
>> @@ -0,0 +1,11 @@
>> +# SPDX-License-Identifier: GPL-2.0
>> +# Copyright (c) 2015-2019, Intel Corporation.
>> +
>> +config RPMB
>> +	tristate "RPMB partition interface"
>> +	help
>> +	  Unified RPMB partition interface for RPMB capable devices such as
>> +          eMMC and UFS. Provides interface for in kernel security controllers to
>
> Indent the line above with one tab + 2 spaces instead of many spaces.
>> +	  access RPMB partition.
>> +
>> +	  If unsure, select N.
>
> Do we want a separate subdir in drivers/ for various "misc" drivers?
> with only one driver in it?
>
> Will there be other drivers in rpmb?
>

There may be others as the usage of rpmb driver grow over time but for 
now, this is the only  driver.
Should i keep it like this ?[A

Thanks,
Shyam


  reply	other threads:[~2023-07-26 20:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-22  1:41 [RFC, PATCH 0/1] Replay Protected Memory Block (RPMB) driver Shyam Saini
2023-07-22  1:41 ` [RFC, PATCH 1/1] rpmb: add " Shyam Saini
2023-07-22  3:11   ` Randy Dunlap
2023-07-26 20:10     ` Shyam Saini [this message]
2023-08-07 15:00   ` Ulf Hansson
2023-08-07 21:02   ` Bart Van Assche
2023-08-22 18:43     ` Shyam Saini
     [not found] < <CAPDyKFoBC+GaGerGDEAjg9q4ayV9mMBKkfFk3nO-zcQzOZ_H6Q@mail.gmail.com>
2023-08-16 23:31 ` Shyam Saini
2023-08-21  9:49   ` Jerome Forissier
2023-08-21 10:03     ` Sumit Garg
2023-08-22 18:47     ` Shyam Saini
     [not found] < <CAHUa44Ek0k2b-igA6Gd1ZXVzibTh2sNDMnE-weQwFFKEZ_1jOA@mail.gmail.com>
2023-08-21 11:54 ` Sumit Garg
2023-08-21 11:55 ` Ilias Apalodimas
2023-08-21 12:35 ` Jerome Forissier
     [not found] < <CAC_iWjKKap47PhiCi=BfPZC_wJhVDB10WSf9oWMgdwSgWCfO_A@mail.gmail.com>
2023-08-21 12:17 ` Sumit Garg
     [not found] < <CAFA6WYNPViMs=3cbNsEdhqnjNOUCsHE_8uqiDTzwCKDNNiDkCw@mail.gmail.com>
2023-08-21 11:18 ` Jens Wiklander
2023-08-22 18:59 ` Shyam Saini
2023-08-24 14:01   ` Sumit Garg
     [not found] < <CAFA6WYMPsBUutjKrm+6qTNHpVr80K2GcSLoYa+MFE3CfLSo8ew@mail.gmail.com>
2023-08-22 19:07 ` Shyam Saini
2023-08-23  8:04   ` Linus Walleij
     [not found] < <CACRpkdb=AnJXG2J_DRsN-RUEh=7_eAs8+_CxPYuueVM0c=DP3Q@mail.gmail.com>
2023-08-24 14:07 ` Sumit Garg

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=e727c5c9-58c1-5d14-99c1-5d9a62998b5@linux.microsoft.com \
    --to=shyamsaini@linux.microsoft.com \
    --cc=op-tee@lists.trustedfirmware.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