From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1 1/1] uClibc 0.9.33 : forward errno bug patches from uClibc 0.9.32
Date: Sun, 24 Mar 2013 12:42:54 +0100 [thread overview]
Message-ID: <20130324124254.2064e896@skate> (raw)
In-Reply-To: <1332621845-10604-2-git-send-email-sagaert.johan@skynet.be>
Dear Sagaert Johan,
On Sat, 24 Mar 2012 21:44:05 +0100, Sagaert Johan wrote:
>
> Signed-off-by: Sagaert Johan <sagaert.johan@skynet.be>
> ---
I've removed this patch from our patchwork. An updated version had been
posted in the mean time, and later reverted because it was causing
issues. I would suggest to raise the issue to upstream and get it fixed
here if needed, and then backport a proper fix in Buildroot.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-03-24 11:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-24 20:44 [Buildroot] [PATCH v1 0/1] forward errno bug patches from uClibc 0.9.32 Sagaert Johan
2012-03-24 20:44 ` [Buildroot] [PATCH v1 1/1] uClibc 0.9.33 : " Sagaert Johan
2013-03-24 11:42 ` Thomas Petazzoni [this message]
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=20130324124254.2064e896@skate \
--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 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.