From: Linus Walleij <linus.walleij@linaro.org>
To: "Jorge Ramirez-Ortiz, Foundries" <jorge@foundries.io>
Cc: Dominique Martinet <asmadeus@codewreck.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
Dominique Martinet <dominique.martinet@atmark-techno.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] mmc: part_switch: fixes switch on gp3 partition
Date: Wed, 6 Mar 2024 14:03:47 +0100 [thread overview]
Message-ID: <CACRpkdYS-5mDjNP2zJ2J=_k_uboyVGK61Z1XWHcUh26HT6WKmQ@mail.gmail.com> (raw)
In-Reply-To: <Zegx5PCtg6hs8zyp@trax>
On Wed, Mar 6, 2024 at 10:05 AM Jorge Ramirez-Ortiz, Foundries
<jorge@foundries.io> wrote:
> That looked strange as there should be support for 4 GP but this code
> kind of convinced me of the opposite.
>
> if (idata->rpmb) {
> /* Support multiple RPMB partitions */
> target_part = idata->rpmb->part_index;
> target_part |= EXT_CSD_PART_CONFIG_ACC_RPMB;
> }
>
> So if we apply the fix that you propose, how are multiple RPMB
> partitions (ie, 4) going to be identified as RPMB? Unless there can't be
> more than 3?
Sorry for writing bad code comments.
This comment means:
"support multiple RPMB partitions [on the same Linux system]"
not:
"support multiple RPMB partitions [on the same eMMC device]"
Yours,
Linus Walleij
next prev parent reply other threads:[~2024-03-06 13:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 1:44 [PATCH] mmc: part_switch: fixes switch on gp3 partition Dominique Martinet
2024-03-06 8:03 ` Linus Walleij
2024-03-06 8:15 ` Dominique Martinet
2024-03-06 9:05 ` Jorge Ramirez-Ortiz, Foundries
2024-03-06 11:39 ` Dominique Martinet
2024-03-06 13:03 ` Linus Walleij [this message]
2024-03-06 13:18 ` Linus Walleij
2024-03-06 14:22 ` Jorge Ramirez-Ortiz, Foundries
2024-03-06 14:38 ` Linus Walleij
2024-03-06 15:56 ` Ulf Hansson
2024-03-06 19:49 ` Linus Walleij
2024-03-06 22:38 ` Ulf Hansson
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='CACRpkdYS-5mDjNP2zJ2J=_k_uboyVGK61Z1XWHcUh26HT6WKmQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=asmadeus@codewreck.org \
--cc=dominique.martinet@atmark-techno.com \
--cc=jorge@foundries.io \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).