From: javier.martinez@collabora•co.uk (Javier Martinez Canillas)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 1/2] ARM: exynos_defconfig: Enable Control Groups support
Date: Mon, 08 Sep 2014 14:43:10 +0200 [thread overview]
Message-ID: <540DA45E.1040702@collabora.co.uk> (raw)
In-Reply-To: <53FE02E6.3030302@suse.de>
Hello Andreas,
On 08/27/2014 06:10 PM, Andreas F?rber wrote:
> Am 27.08.2014 13:02, schrieb Javier Martinez Canillas:
>> systemd needs control groups support to be enabled in the
>> kernel so let's enable it by default since is quite likely
>> that a user-space with systemd will be used.
>>
>> Signed-off-by: Javier Martinez Canillas <javier.martinez@collabora•co.uk>
>> ---
>> arch/arm/configs/exynos_defconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/arch/arm/configs/exynos_defconfig b/arch/arm/configs/exynos_defconfig
>> index 676c744..590abde 100644
>> --- a/arch/arm/configs/exynos_defconfig
>> +++ b/arch/arm/configs/exynos_defconfig
>> @@ -1,6 +1,7 @@
>> CONFIG_SYSVIPC=y
>> CONFIG_NO_HZ=y
>> CONFIG_HIGH_RES_TIMERS=y
>> +CONFIG_CGROUPS=y
>> CONFIG_BLK_DEV_INITRD=y
>> CONFIG_KALLSYMS_ALL=y
>> CONFIG_MODULES=y
>
> CONFIG_FHANDLE=y is also needed for systemd to get a serial console.
> multi_v7 has that already.
>
That's a requirement for systemd >= 209 AFAIK. I've systemd 208 on my debian
jessie and it works without it.
I agree that it should be included but I think it can be in a follow-up patch.
> Regards,
> Andreas
>
Best regards,
Javier
prev parent reply other threads:[~2014-09-08 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 11:02 [PATCH 1/2] ARM: exynos_defconfig: Enable Control Groups support Javier Martinez Canillas
2014-08-27 11:02 ` [PATCH 2/2] ARM: multi_v7_defconfig: " Javier Martinez Canillas
2014-08-27 16:10 ` [PATCH 1/2] ARM: exynos_defconfig: " Andreas Färber
2014-09-08 12:43 ` Javier Martinez Canillas [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=540DA45E.1040702@collabora.co.uk \
--to=javier.martinez@collabora$(echo .)co.uk \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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