From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] Rebuild external kernel modules on kernel change
Date: Sun, 05 Apr 2009 18:43:47 +0200 [thread overview]
Message-ID: <gran43$m4d$1@ger.gmane.org> (raw)
In-Reply-To: <be7a9f3d0904041046n65089397g5b82ccab0aec2afb@mail.gmail.com>
On 04-04-09 19:46, Otavio Salvador wrote:
> On Sat, Apr 4, 2009 at 10:31 AM, Koen Kooi<k.kooi@student.utwente.nl> wrote:
>> Hi,
> [...]
>> I don't really like this method, but I'm having a hard time coming up with a
>> decent solution that:
> [...]
>
> I agree that is not beauty but it works.
>
> I also belive it could be used in other recipes too as initramfs-images. This
> way forcing the rebuild of it if the kernel is changed and machine revision
> is bumped.
>
> Fully support it.
>
> +1
Thanks, I'll try cooking up a patch for beagleboard tomorrow to show a
real life example.
regards,
Koen
next prev parent reply other threads:[~2009-04-05 16:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 13:31 [RFC] Rebuild external kernel modules on kernel change Koen Kooi
2009-04-04 15:51 ` Frans Meulenbroeks
2009-04-04 16:44 ` Koen Kooi
2009-04-04 20:18 ` Frans Meulenbroeks
2009-04-04 21:14 ` Koen Kooi
2009-04-04 17:46 ` Otavio Salvador
2009-04-05 16:43 ` Koen Kooi [this message]
2009-04-05 17:07 ` Koen Kooi
2009-04-04 20:46 ` Jeremy Lainé
2009-04-05 22:43 ` Richard Purdie
2009-04-06 7:16 ` Koen Kooi
2009-06-01 16:58 ` Tom Rini
2009-06-01 17:25 ` Koen Kooi
2009-06-01 18:17 ` Phil Blundell
2009-06-01 18:45 ` Koen Kooi
2009-06-01 19:10 ` Phil Blundell
2009-06-01 20:17 ` Phil Blundell
2009-06-01 20:52 ` Koen Kooi
2009-06-01 21:32 ` Tom Rini
2009-06-01 21:32 ` Phil Blundell
2009-06-01 20:55 ` Tom Rini
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='gran43$m4d$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