From: "Arnd Bergmann" <arnd@arndb.de>
To: "Jens Wiklander" <jens.wiklander@linaro.org>,
linux-kernel@vger.kernel.org,
"linux-mmc @ vger . kernel . org" <linux-mmc@vger.kernel.org>,
op-tee@lists.trustedfirmware.org
Cc: "Ulf Hansson" <ulf.hansson@linaro.org>,
"Sumit Garg" <sumit.garg@linaro.org>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"kernel test robot" <lkp@intel.com>
Subject: Re: [PATCH 1/2] mmc: block: add RPMB dependency
Date: Mon, 02 Sep 2024 15:14:50 +0000 [thread overview]
Message-ID: <75d9c06f-5af3-4088-8813-b4a3ccb59434@app.fastmail.com> (raw)
In-Reply-To: <20240902151231.3705204-1-jens.wiklander@linaro.org>
On Mon, Sep 2, 2024, at 15:12, Jens Wiklander wrote:
> Prevent build error when CONFIG_RPMB=m and CONFIG_MMC_BLOCK=y by adding
> a dependency to CONFIG_RPMB for CONFIG_MMC_BLOCK block so the RPMB
> subsystem always is reachable if configured. This means that
> CONFIG_MMC_BLOCK automatically becomes compiled as a module if
> CONFIG_RPMB is compiled as a module. If CONFIG_RPMB isn't configured or
> is configured as built-in, CONFIG_MMC_BLOCK will remain unchanged.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes:
> https://lore.kernel.org/oe-kbuild-all/202409021448.RSvcBPzt-lkp@intel.com/
> Fixes: 7852028a35f0 ("mmc: block: register RPMB partition with the RPMB
> subsystem")
> Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>
Acked-by: Arnd Bergmann <arnd@arndb.de>
next prev parent reply other threads:[~2024-09-02 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 15:12 Jens Wiklander
2024-09-02 15:12 ` [PATCH 2/2] optee: " Jens Wiklander
2024-09-03 12:37 ` Ulf Hansson
2024-09-02 15:14 ` Arnd Bergmann [this message]
2024-09-03 12:37 ` [PATCH 1/2] mmc: block: " 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=75d9c06f-5af3-4088-8813-b4a3ccb59434@app.fastmail.com \
--to=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jens.wiklander@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lkp@intel.com \
--cc=op-tee@lists.trustedfirmware.org \
--cc=sumit.garg@linaro.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
all inboxes | Powered by JetHome®