Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request] Pull request for branch uclibc-0.9.30.2
Date: Thu, 14 Jan 2010 10:23:48 +0100	[thread overview]
Message-ID: <20100114102348.7328dbd4@surf> (raw)
In-Reply-To: <cover.1263460719.git.thomas.petazzoni@free-electrons.com>

On Thu, 14 Jan 2010 10:18:43 +0100
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> wrote:

>       Add uClibc 0.9.30.2

I'm testing it right now. I've just sent the patch early to avoid
duplicate work.

Concerning the patches that we have on uClibc 0.9.30.1:

 * uClibc-0.9.30.1-64bit-strtouq.patch

   Fixed by a7cd0cf2a31493506795528125a1d87428b67374

 * uClibc-0.9.30.1-arm-fix-linuxthreads-sysdep.patch

   Apparently fixed by 721ad11a13423115831da863fb5c5bbd0f340adb

 * uClibc-0.9.30.1-c99-ldbl-math.patch

   Fixed by aa148d76e87a63863808529a6687d053adc5a46d

 * uClibc-0.9.30.1-dl-sysdep-inline.patch

   Fixed by f12e73b50c47896faf4498a5085f9bfbd828a1c3

 * uClibc-0.9.30.1-fix-getaddrinfo.patch

   Fixed by 65119bba48b4ec904e81e99b701c8388afdb09a0

 * uClibc-0.9.30.1-unifdef-getline.patch

   Fixed by 27a28684fa518d92af24266eadc5d2efcc152104

So it looks like all the patches we were carrying for uClibc 0.9.30.1
have been merged upstream.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2010-01-14  9:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-14  9:18 [Buildroot] [pull request] Pull request for branch uclibc-0.9.30.2 Thomas Petazzoni
2010-01-14  9:18 ` [Buildroot] [PATCH 1/1] Add uClibc 0.9.30.2 Thomas Petazzoni
2010-01-14  9:23 ` Thomas Petazzoni [this message]
2010-01-15 14:22   ` [Buildroot] [pull request] Pull request for branch uclibc-0.9.30.2 Peter Korsgaard
2010-01-15 14:21 ` Peter Korsgaard

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=20100114102348.7328dbd4@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --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