From: hkallweit1@gmail.com (Heiner Kallweit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: fix compile testing of scpi clk driver
Date: Wed, 29 Nov 2017 21:37:46 +0100 [thread overview]
Message-ID: <d01ed8fa-9f9e-adf6-3133-800433fef7bb@gmail.com> (raw)
In-Reply-To: <20171129170453.GA7698@codeaurora.org>
Am 29.11.2017 um 18:04 schrieb Stephen Boyd:
> On 11/28, Heiner Kallweit wrote:
>> We now have a hard dependency on ARM_SCPI_PROTOCOL and may end up with
>> the following error:
>> ERROR: "get_scpi_ops" [drivers/clk/clk-scpi.ko] undefined!
>> Fix this by removing COMPILE_TEST from COMMON_CLK_SCPI dependencies.
>>
>> Fixes: f7fee8be06a6 "firmware: arm_scpi: remove default for get_scpi_ops if not reachable"
>
> I don't see this commit anywhere. Is this a future issue?
>
Sorry, yes it is and the patch was primarily addressed to Sudeep. See here:
https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git/log/?h=for-next/scpi
next prev parent reply other threads:[~2017-11-29 20:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 6:58 [PATCH] clk: fix compile testing of scpi clk driver Heiner Kallweit
2017-11-29 17:04 ` Stephen Boyd
2017-11-29 20:37 ` Heiner Kallweit [this message]
2017-12-04 2:25 ` Sudeep Holla
2017-12-04 2:25 ` Sudeep Holla
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=d01ed8fa-9f9e-adf6-3133-800433fef7bb@gmail.com \
--to=hkallweit1@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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).