From: Shyam Saini <shyamsaini@linux.microsoft.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org,
op-tee@lists.trustedfirmware.org, linux-scsi@vger.kernel.org,
"Alex Bennée" <alex.bennee@linaro.org>,
"Tomas Winkler" <tomas.winkler@intel.com>,
"Ulf Hansson" <ulf.hansson@linaro.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Arnd Bergmann" <arnd.bergmann@linaro.org>,
"Ilias Apalodimas" <ilias.apalodimas@linaro.org>,
"Sumit Garg" <sumit.garg@linaro.org>,
"Tyler Hicks" <code@tyhicks.com>,
"Srivatsa S . Bhat" <srivatsa@csail.mit.edu>,
"Paul Moore" <paul@paul-moore.com>,
"Allen Pais" <apais@linux.microsoft.com>
Subject: Re: [RFC, PATCH 1/1] rpmb: add Replay Protected Memory Block (RPMB) driver
Date: Wed, 26 Jul 2023 13:10:13 -0700 (PDT) [thread overview]
Message-ID: <e727c5c9-58c1-5d14-99c1-5d9a62998b5@linux.microsoft.com> (raw)
In-Reply-To: <233853ab-235b-d4dd-cd69-588d1a83ce4f@infradead.org>
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
next prev parent 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:40 [RFC, PATCH 0/1] Replay Protected Memory Block (RPMB) driver Shyam Saini
2023-07-22 1:40 ` [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-16 23:31 ` Shyam Saini
2023-08-21 9:49 ` Jerome Forissier
2023-08-21 10:03 ` Sumit Garg
2023-08-21 11:18 ` Jens Wiklander
2023-08-21 11:54 ` Sumit Garg
2023-08-21 11:55 ` Ilias Apalodimas
2023-08-21 12:17 ` Sumit Garg
2023-08-22 19:07 ` Shyam Saini
2023-08-23 8:04 ` Linus Walleij
2023-08-24 14:07 ` Sumit Garg
2023-08-21 12:35 ` Jerome Forissier
2023-08-22 18:59 ` Shyam Saini
2023-08-24 14:01 ` Sumit Garg
2023-08-22 18:47 ` Shyam Saini
2023-08-07 21:02 ` Bart Van Assche
2023-08-22 18:43 ` Shyam Saini
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=alex.bennee@linaro.org \
--cc=apais@linux.microsoft.com \
--cc=arnd.bergmann@linaro.org \
--cc=code@tyhicks.com \
--cc=ilias.apalodimas@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=op-tee@lists.trustedfirmware.org \
--cc=paul@paul-moore.com \
--cc=rdunlap@infradead.org \
--cc=srivatsa@csail.mit.edu \
--cc=sumit.garg@linaro.org \
--cc=tomas.winkler@intel.com \
--cc=ulf.hansson@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