Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hinko Kocevar <hinko.kocevar@cetrtapot.si>
To: buildroot@busybox.net
Subject: [Buildroot] 2009.02-rc2 released
Date: Wed, 28 Jan 2009 09:47:58 +0100	[thread overview]
Message-ID: <49801BBE.8060603@cetrtapot.si> (raw)
In-Reply-To: <87skn9iv5w.fsf@macbook.be.48ers.dk>

Peter Korsgaard wrote:
> Hi,
> 
> Another week, another release candidate. I have released
> buildroot-2009.02-rc2:
> 
> http://buildroot.uclibc.org/downloads/buildroot-2009.02-rc2.tar.gz
> 
> or
> 
> http://buildroot.uclibc.org/downloads/buildroot-2009.02-rc2.tar.bz2
> 

Great!

> Please give it a spin and report back issues to the mailing list or
> the bug tracker.

I've tested my custom Axis etrax LX100 based board (cris arch-v10 CPU) and
buildroot 2009.02-rc2 builds toolchain and kernel wo problem.
I have minor fixes for 2.6.28.1 kernel and 4.3.2 gcc regarding cris
architecture (please apply):

 - 999-gcc-4.3.0-cris-pragma-pack-warning-remove.patch
   remove warnings when compiling gcc-4.3.2
 - linux-2.6.28.1-cris-eth-driver-netpoll.patch
   make cris eth driver compile on 2.6.28.1 kernel
 - linux-2.6.28.1-cris-klist-warnings.patch
   avoid klist warnings at bootup related to alignment of the klist struct (from be 2.6.28 stable)

> 
> I think we're pretty well on track to do a final release in 2 weeks.
> 

Keep up the great work!

Thanks,
Hinko

-- 
Hinko Ko?evar, OSS developer
?ETRTA POT, d.o.o.
Planina 3, 4000 Kranj, SI EU
tel     ++386 (0) 4 280 66 03
e-mail  hinko.kocevar at cetrtapot.si
http    www.cetrtapot.si

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 999-gcc-4.3.0-cris-pragma-pack-warning-remove.patch
Url: http://lists.busybox.net/pipermail/buildroot/attachments/20090128/3c53abf1/attachment.diff 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: linux-2.6.28.1-cris-klist-warnings.patch
Url: http://lists.busybox.net/pipermail/buildroot/attachments/20090128/3c53abf1/attachment-0001.diff 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: linux-2.6.28.1-cris-eth-driver-netpoll.patch
Url: http://lists.busybox.net/pipermail/buildroot/attachments/20090128/3c53abf1/attachment-0002.diff 

  parent reply	other threads:[~2009-01-28  8:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-23 21:12 [Buildroot] 2009.02-rc2 released Peter Korsgaard
2009-01-23 21:27 ` Cyril HAENEL
2009-01-24  9:02   ` Peter Korsgaard
2009-01-24 13:03     ` Cyril HAENEL
2009-01-26 17:24 ` Robert Nelson
2009-01-26 17:43   ` Peter Korsgaard
2009-01-26 18:30     ` Robert Nelson
2009-01-26 18:49       ` Peter Korsgaard
2009-01-28  8:47 ` Hinko Kocevar [this message]
2009-01-28 16:37   ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2009-01-25  0:28 Paul Jones
2009-01-25  7:32 ` Ulf Samuelsson
2009-01-25 13:07   ` Peter Korsgaard
2009-01-25 21:17     ` Ulf Samuelsson
2009-01-25 21:28       ` Peter Korsgaard
2009-01-25 22:24         ` Ulf Samuelsson
2009-01-25 23:52           ` Paul Jones
2009-01-26  5:54             ` Peter Korsgaard
2009-01-26  8:48               ` Cyril HAENEL
2009-01-26 16:23           ` Peter Korsgaard
2009-01-26 12:04       ` Thomas Lundquist

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=49801BBE.8060603@cetrtapot.si \
    --to=hinko.kocevar@cetrtapot.si \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox