From: Krzysztof Kozlowski <krzk@kernel.org>
To: Javier Martinez Canillas <javier@osg.samsung.com>,
linux-kernel@vger.kernel.org
Cc: Arnd Bergmann <arnd@arndb.de>, Olof Johansson <olof@lixom.net>,
linux-arm-kernel@lists.infradead.org, arm@kernel.org
Subject: Re: [PATCH 2/2] ARM: multi_v7_defconfig: Don't attempt to enable schedutil governor as module
Date: Fri, 19 Aug 2016 15:40:49 +0200 [thread overview]
Message-ID: <9c71ddbd-deb1-1e07-7421-53bb58359bad@kernel.org> (raw)
In-Reply-To: <1471612328-6467-2-git-send-email-javier@osg.samsung.com>
On 08/19/2016 03:12 PM, Javier Martinez Canillas wrote:
> The schedutil CPUFreq governor could be built as a module but the commit
> 58919e83c85c ("cpufreq / sched: Pass flags to cpufreq_update_util()")
> made it non-modular so attempting to enable as module leads to a warning:
>
> warning: symbol value 'm' invalid for CPU_FREQ_GOV_SCHEDUTIL
>
> Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com>
>
> ---
>
> arch/arm/configs/multi_v7_defconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Looks good.
Applied... wait, no, these are not in samsung-soc list so they miss also
from patchwork. For reference:
Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Please post it to linux-samsung-soc, unless it goes through arm-soc or
other tree.
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-08-19 13:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 13:12 [PATCH 1/2] ARM: exynos_defconfig: Don't attempt to enable schedutil governor as module Javier Martinez Canillas
2016-08-19 13:12 ` [PATCH 2/2] ARM: multi_v7_defconfig: " Javier Martinez Canillas
2016-08-19 13:40 ` Krzysztof Kozlowski [this message]
2016-08-19 13:46 ` Javier Martinez Canillas
2016-08-19 13:52 ` Javier Martinez Canillas
2016-08-19 15:51 ` Krzysztof Kozlowski
2016-08-19 15:55 ` Javier Martinez Canillas
2016-08-19 13:41 ` [PATCH 1/2] ARM: exynos_defconfig: " Krzysztof Kozlowski
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=9c71ddbd-deb1-1e07-7421-53bb58359bad@kernel.org \
--to=krzk@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=javier@osg.samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
/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