From: Rod Whitby <rod@whitby.id.au>
To: OpenEmbedded Developers <openembedded-devel@openembedded.org>
Subject: Re: RFC: Replacing ixp4xx-kernel with linux-ixp4xx
Date: Wed, 28 Nov 2007 16:33:24 +1030 [thread overview]
Message-ID: <474D04AC.2010700@whitby.id.au> (raw)
In-Reply-To: <474C18A5.4030402@whitby.id.au>
Rod Whitby wrote:
> Now that SRCREV is assumed available in bitbake and OE, it is time to
> revisit the ixp4xx-kernel recipes and use modern-day ways of doing things.
>
> To accomplish this, I intend gradually replacing the ixp4xx-kernel
> recipes with linux-ixp4xx recipes which more closely follow OE best
> practices, and allow for sensible usage of linux-ixp4xx kernel recipes
> for all ixp4xx devices (not just those used by nslu2-linux firmware).
...
> This will happen over the coming weeks, and I'll make sure the whole set
> of linux-ixp4xx recipes and supporting files are in place well before
> removing or changing any of the existing ixp4xx-kernel recipes.
Well, I had a spurt of productivity last night, and can build angstrom
using the new linux-ixp4xx kernel, so I've checked in linux-ixp4xx
replacements for all the old ixp4xx-kernel recipes.
I'll wait a reasonable time for review and testing of the new recipes
before removing any old ixp4xx-kernel recipes (and will double check
that nothing else is still using them before doing so). I will mail
again with a notification before doing so.
Style comments on the new linux-ixp4xx kernel recipes are welcome.
(I guess I should have run them through oe-style-thingo before saying
that ...)
-- Rod
next prev parent reply other threads:[~2007-11-28 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 13:16 RFC: Replacing ixp4xx-kernel with style-compliant updated linux-ixp4xx Rod Whitby
2007-11-28 6:03 ` Rod Whitby [this message]
2007-11-28 18:43 ` RFC: Replacing ixp4xx-kernel with linux-ixp4xx Leon Woestenberg
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=474D04AC.2010700@whitby.id.au \
--to=rod@whitby.id.au \
--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 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.