From: "Jorge Ramirez-Ortiz, Foundries" <jorge@foundries.io>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jorge Ramirez-Ortiz <jorge@foundries.io>,
ulf.hansson@linaro.org, linus.walleij@linaro.org,
adrian.hunter@intel.com, linux-mmc@vger.kernel.org,
linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCHv3] mmc: rpmb: fixes pause retune on all RPMB partitions.
Date: Fri, 1 Dec 2023 15:24:14 +0100 [thread overview]
Message-ID: <ZWnsjtnag6gXDnuq@trax> (raw)
In-Reply-To: <2023120139-untried-unholy-456e@gregkh>
On 01/12/23 12:22:57, Greg KH wrote:
> On Fri, Dec 01, 2023 at 11:05:27AM +0100, Jorge Ramirez-Ortiz wrote:
> > When RPMB was converted to a character device, it added support for
> > multiple RPMB partitions (Commit 97548575bef3 ("mmc: block: Convert RPMB
> > to a character device").
> >
> > One of the changes in this commit was transforming the variable
> > target_part defined in __mmc_blk_ioctl_cmd into a bitmask.
> >
> > This inadvertedly regressed the validation check done in
> > mmc_blk_part_switch_pre() and mmc_blk_part_switch_post().
> >
> > This commit fixes that regression.
> >
> > Fixes: 97548575bef3 ("mmc: block: Convert RPMB to a character device")
> > Signed-off-by: Jorge Ramirez-Ortiz <jorge@foundries.io>
> > Cc: <stable@vger.kernel.org> # v6.0+
>
> Why only 6.0 when the "Fixes:" tag goes back to a 4.14 commit?
ops so sorry (was WIP and got distracted press sent and forgot), will
fix and add Linus' Reviewed-by.
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2023-12-01 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 10:05 [PATCHv3] mmc: rpmb: fixes pause retune on all RPMB partitions Jorge Ramirez-Ortiz
2023-12-01 12:22 ` Greg KH
2023-12-01 14:24 ` Jorge Ramirez-Ortiz, Foundries [this message]
2023-12-01 13:19 ` Linus Walleij
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=ZWnsjtnag6gXDnuq@trax \
--to=jorge@foundries.io \
--cc=adrian.hunter@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--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