From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4 v2] core/pkg-kernel-module: ensure linux supports modules
Date: Mon, 24 Aug 2015 22:31:33 +0200 [thread overview]
Message-ID: <55DB7F25.6030302@mind.be> (raw)
In-Reply-To: <02a8be3c5e04219765d90c0b665f32eb6f4db352.1440434894.git.yann.morin.1998@free.fr>
On 08/24/2015 06:50 PM, Yann E. MORIN wrote:
> When a package wants to build a kernel module, we should ensure that the
> kernel does support modules.
>
> This patch does it automatically for packages using the kernel-module
> infrastructure.
>
> Packages that do not use it will have to set it manually (to be done in
> a followup patch).
>
> Suggested-by: Peter Korsgaard <jacmet@uclibc.org>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Peter Korsgaard <jacmet@uclibc.org>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: No? Rubinstein <noe.rubinstein@gmail.com>
> Cc: Jan Viktorin <viktorin@rehivetech.com>
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Regards,
Arnout
> ---
> linux/linux.mk | 2 ++
> package/pkg-kernel-module.mk | 5 +++++
> 2 files changed, 7 insertions(+)
>
> diff --git a/linux/linux.mk b/linux/linux.mk
> index 48f9c74..bbcc54b 100644
> --- a/linux/linux.mk
> +++ b/linux/linux.mk
> @@ -175,6 +175,8 @@ LINUX_KCONFIG_EDITORS = menuconfig xconfig gconfig nconfig
> LINUX_KCONFIG_OPTS = $(LINUX_MAKE_FLAGS)
>
> define LINUX_KCONFIG_FIXUP_CMDS
> + $(if $(LINUX_NEEDS_MODULES),
> + $(call KCONFIG_ENABLE_OPT,CONFIG_MODULES,$(@D)/.config))
> $(if $(BR2_arm)$(BR2_armeb),
> $(call KCONFIG_ENABLE_OPT,CONFIG_AEABI,$(@D)/.config))
> $(if $(BR2_TARGET_ROOTFS_CPIO),
> diff --git a/package/pkg-kernel-module.mk b/package/pkg-kernel-module.mk
> index 6fb7704..f6730b8 100644
> --- a/package/pkg-kernel-module.mk
> +++ b/package/pkg-kernel-module.mk
> @@ -44,6 +44,11 @@
>
> define inner-kernel-module
>
> +# If the package is enabled, ensure the kernel will support modules
> +ifeq ($$(BR2_PACKAGE_$(2)),y)
> +LINUX_NEEDS_MODULES = y
> +endif
> +
> # The kernel must be built first.
> $(2)_DEPENDENCIES += linux
>
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-08-24 20:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 16:49 [Buildroot] [PATCH 0/4 v2] core/pkg-kernel-config: ensure linux supports modules (branch yem/kernel-module) Yann E. MORIN
2015-08-24 16:50 ` [Buildroot] [PATCH 1/4 v2] core/pkg-kernel-module: ensure linux supports modules Yann E. MORIN
2015-08-24 20:31 ` Arnout Vandecappelle [this message]
2015-08-24 16:50 ` [Buildroot] [PATCH 2/4 v2] core/pkg-kernel-module: drop now-useles check for CONFIG_MODULES Yann E. MORIN
2015-08-24 20:33 ` Arnout Vandecappelle
2015-08-24 16:50 ` [Buildroot] [PATCH 3/4 v2] packages: ensure linux supports modules even when not using kernel-module Yann E. MORIN
2015-08-24 20:42 ` Arnout Vandecappelle
2015-08-25 12:20 ` Jan Viktorin
2015-08-24 16:50 ` [Buildroot] [PATCH 4/4 v2] package/linux-fusion: slight simplification Yann E. MORIN
2015-08-24 20:45 ` Arnout Vandecappelle
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=55DB7F25.6030302@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.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