linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: David Virag <virag.david003@gmail.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	linux-samsung-soc@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] soc: samsung: exynos-pmu: Fix compilation when nothing selects CONFIG_MFD_CORE
Date: Wed, 15 Sep 2021 09:51:00 +0200	[thread overview]
Message-ID: <163169222223.16372.8442242827654330539.b4-ty@canonical.com> (raw)
In-Reply-To: <20210909222812.108614-1-virag.david003@gmail.com>

On Fri, 10 Sep 2021 00:28:12 +0200, David Virag wrote:
> Commit 93618e344a5e ("soc: samsung: exynos-pmu: instantiate clkout driver as MFD")
> adds a "devm_mfd_add_devices" call in the exynos-pmu driver which depends
> on CONFIG_MFD_CORE. If no driver selects that config, the build will fail
> if CONFIG_EXYNOS_PMU is enabled with the following error:
> drivers/soc/samsung/exynos-pmu.c:137: undefined reference to `devm_mfd_add_devices'
> 
> Fix this by making CONFIG_EXYNOS_PMU select CONFIG_MFD_CORE.
> Fixes: 93618e344a5e ("soc: samsung: exynos-pmu: instantiate clkout driver as MFD")
> 
> [...]

Applied, thanks!

[1/1] soc: samsung: exynos-pmu: Fix compilation when nothing selects CONFIG_MFD_CORE
      commit: e37ef6dcdb1f4738b01cec7fb7be46af07816af9

Best regards,
-- 
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>

      reply	other threads:[~2021-09-15  7:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-09 22:28 [PATCH] soc: samsung: exynos-pmu: Fix compilation when nothing selects CONFIG_MFD_CORE David Virag
2021-09-15  7:51 ` Krzysztof Kozlowski [this message]

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=163169222223.16372.8442242827654330539.b4-ty@canonical.com \
    --to=krzysztof.kozlowski@canonical.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=s.nawrocki@samsung.com \
    --cc=sboyd@kernel.org \
    --cc=virag.david003@gmail.com \
    /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).