From: Wolfram Sang <wsa-dev@sang-engineering.com>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: kernel test robot <lkp@intel.com>,
"oe-kbuild-all@lists.linux.dev" <oe-kbuild-all@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: drivers/mmc/host/renesas_sdhi_core.c:951: undefined reference to `rdev_get_drvdata'
Date: Sat, 29 Mar 2025 08:17:28 +0100 [thread overview]
Message-ID: <Z-eeiMFsQQNMt2nn@shikoro> (raw)
In-Reply-To: <TY3PR01MB11346FEE53574DBF768BA9B8686A32@TY3PR01MB11346.jpnprd01.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 457 bytes --]
> CONFIG_REGULATOR is not enabled in arm-randconfig-r111-20250328 that is leading
> to this build issue.
>
> I will send a fix by "select REGULATOR" in config MMC_SDHI
What about using MMC_SDHI_INTERNAL_DMAC? So we leave out at least older
SDHI instances. Ideally, we would say "select ... if <family>" but this
will easily be missed in updates. Maybe the above is a fair compromise.
Those systems will likely have regulators enabled anyhow.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-03-29 7:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 21:43 drivers/mmc/host/renesas_sdhi_core.c:951: undefined reference to `rdev_get_drvdata' kernel test robot
2025-03-29 6:41 ` Biju Das
2025-03-29 7:17 ` Wolfram Sang [this message]
2025-03-29 7:24 ` Biju Das
2025-03-29 7:28 ` Wolfram Sang
2025-03-29 7:37 ` Biju Das
2025-03-29 7:47 ` Wolfram Sang
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=Z-eeiMFsQQNMt2nn@shikoro \
--to=wsa-dev@sang-engineering.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--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