From: "Stefan Müller-Klieser" <s.mueller-klieser@phytec.de>
To: Sam Nelson <sam.nelson@ti.com>, meta-ti@yoctoproject.org
Subject: Re: [PATCH] linux-ti-staging: Work around to avoid race condition with external module
Date: Mon, 14 Dec 2015 13:06:38 +0100 [thread overview]
Message-ID: <566EB0CE.5030706@phytec.de> (raw)
In-Reply-To: <1450093668-30879-1-git-send-email-sam.nelson@ti.com>
Hi,
this work around introduces another race condition, as you have to make
sure every external module recipe depends on do_compile_kernelmodules,
and not shared_workdir.
Regards,
Stefan
On 14.12.2015 12:47, Sam Nelson wrote:
> - Currently there is an issue with compiling external kernel module
> which depends on symbols from another kernel module which is part of the
> list of modules configured to be built as modules in the default config.
> - This work around allows to avoid the issue by copying the module
> symbols to the kernel directory after making the kernel modules build.
> - This issue is already fixed in oe-core: master branch as of date
> - This is just work around before updating to latest oe-core
>
> Signed-off-by: Sam Nelson <sam.nelson@ti.com>
> ---
> recipes-kernel/linux/linux-ti-staging_3.14.bb | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/recipes-kernel/linux/linux-ti-staging_3.14.bb b/recipes-kernel/linux/linux-ti-staging_3.14.bb
> index 54530e4..88950ae 100644
> --- a/recipes-kernel/linux/linux-ti-staging_3.14.bb
> +++ b/recipes-kernel/linux/linux-ti-staging_3.14.bb
> @@ -65,3 +65,7 @@ KERNEL_GIT_PROTOCOL = "git"
> SRC_URI += "${KERNEL_GIT_URI};protocol=${KERNEL_GIT_PROTOCOL};branch=${BRANCH} \
> file://defconfig \
> "
> +
> +do_compile_kernelmodules_append() {
> + cp Module.symvers ${STAGING_KERNEL_BUILDDIR}/
> +}
>
next prev parent reply other threads:[~2015-12-14 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 11:47 [PATCH] linux-ti-staging: Work around to avoid race condition with external module Sam Nelson
2015-12-14 12:06 ` Stefan Müller-Klieser [this message]
2015-12-15 16:32 ` Denys Dmytriyenko
2015-12-16 18:24 ` Nelson, Sam
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=566EB0CE.5030706@phytec.de \
--to=s.mueller-klieser@phytec.de \
--cc=meta-ti@yoctoproject.org \
--cc=sam.nelson@ti.com \
/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.