From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: rm_work and building kernel modules
Date: Mon, 26 Jan 2009 19:34:06 +0100 [thread overview]
Message-ID: <glkvmu$gff$1@ger.gmane.org> (raw)
In-Reply-To: <f96d234e0901261011x1708a5cbra3334ceb18821f08@mail.gmail.com>
On 26-01-09 19:11, Cliff Brake wrote:
> I'm noticed a little glitch with rm_work and building kernel modules
> with OE. Typically, kernel module builds require the kernel source to
> be intact, which gets removed if rm_work is enabled.
Which is why it's getting staged to STAGING_KERNEL_DIR, see module.bbclass.
regards,
Koen
next prev parent reply other threads:[~2009-01-26 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 18:11 rm_work and building kernel modules Cliff Brake
2009-01-26 18:34 ` Koen Kooi [this message]
2009-01-26 19:24 ` Cliff Brake
2009-01-26 20:06 ` Koen Kooi
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='glkvmu$gff$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/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