From: Romain Naour <romain.naour@openwide.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/5 v2] linux: simplify adding new extensions
Date: Thu, 26 Mar 2015 22:54:11 +0100 [thread overview]
Message-ID: <55148003.2000506@openwide.fr> (raw)
In-Reply-To: <e6cc457e3c17aab4a7b800bd82b4a755557235bf.1426342904.git.yann.morin.1998@free.fr>
Hi Yann, All,
Le 14/03/2015 15:25, Yann E. MORIN a ?crit :
> Curently, all three linux extensions follow the same layout:
> - test if the extension is enabled
> - add itself to linux' patch-dependencies
> - declare a macro, added as the pre-patch hook
>
> Except for the macro, all can be commonalised.
>
> Add a simple infrastructure for that:
> - extensions declare themselves in the list of extensions
> - extensions define their macro
> - the infra adds them to the patch-dependencies and pre-patch
> hooks as appropriate
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> linux/linux.mk | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/linux/linux.mk b/linux/linux.mk
> index b1aca41..2917857 100644
> --- a/linux/linux.mk
> +++ b/linux/linux.mk
> @@ -333,6 +333,13 @@ endef
> # included here *must* be in the same directory!
> include $(sort $(wildcard linux/linux-ext-*.mk))
>
> +LINUX_PATCH_DEPENDENCIES += $(foreach ext,$(LINUX_EXTENSIONS),\
> + $(if $(BR2_LINUX_KERNEL_EXT_$(call UPPERCASE,$(ext))),$(ext)))
> +
> +LINUX_PRE_PATCH_HOOKS += $(foreach ext,$(LINUX_EXTENSIONS),\
> + $(if $(BR2_LINUX_KERNEL_EXT_$(call UPPERCASE,$(ext))),\
> + $(call UPPERCASE,$(ext))_PREPARE_KERNEL))
> +
> $(eval $(kconfig-package))
>
> # Support for rebuilding the kernel after the cpio archive has
>
Reviewed-by: Romain Naour <romain.naour@openwide.fr>
Tested with Xenomai extensions and obviously the patch 5/5 applied :)
Tested-by: Romain Naour <romain.naour@openwide.fr>
Best regards,
Romain
next prev parent reply other threads:[~2015-03-26 21:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-14 14:25 [Buildroot] [PATCH 0/5 v2] linux: fix using extensions (branch yem/kernel-ext) Yann E. MORIN
2015-03-14 14:25 ` [Buildroot] [PATCH 1/5 v2] package infra: add patch-dependencies Yann E. MORIN
2015-03-24 23:22 ` Romain Naour
2015-04-04 13:47 ` Thomas Petazzoni
2015-04-05 9:16 ` Yann E. MORIN
2015-04-05 9:46 ` Thomas Petazzoni
2015-04-14 0:17 ` Arnout Vandecappelle
2015-03-14 14:25 ` [Buildroot] [PATCH 2/5 v2] docs/manual: add _PATCH_DEPENDENCIES Yann E. MORIN
2015-03-24 23:22 ` Romain Naour
2015-03-14 14:25 ` [Buildroot] [PATCH 3/5 v2] linux: fix extensions Yann E. MORIN
2015-03-24 23:22 ` Romain Naour
2015-03-14 14:25 ` [Buildroot] [PATCH 4/5 v2] linux: simplify adding new extensions Yann E. MORIN
2015-03-26 21:54 ` Romain Naour [this message]
2015-03-14 14:25 ` [Buildroot] [PATCH 5/5 v2] linux: migrate extensions to use the new infrastructure Yann E. MORIN
2015-03-26 21:55 ` Romain Naour
2015-04-09 21:11 ` [Buildroot] [PATCH 0/5 v2] linux: fix using extensions (branch yem/kernel-ext) Thomas Petazzoni
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=55148003.2000506@openwide.fr \
--to=romain.naour@openwide.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.