From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/3] uclibc: build fixes for xtensa snapshot version
Date: Mon, 13 Jan 2014 10:23:38 +0200 [thread overview]
Message-ID: <20140113082338.GJ4944@tarshish> (raw)
In-Reply-To: <20140113161308.356138d7@skate>
Hi Thomas,
On Mon, Jan 13, 2014 at 04:13:08PM +0800, Thomas Petazzoni wrote:
> On Mon, 13 Jan 2014 08:26:11 +0200, Baruch Siach wrote:
>
> > Baruch Siach (3):
> > uclibc: bump xtensa snapshot version
> > uclibc: xtensa: fix posix_spawn autoconf detection
>
> Why is this patch xtensa specific?
It it not. It's uClibc snapshot specific, and I don't think that blindly
applying this patch to any random snapshot version is a good idea. Only xtensa
and arc have a fixed default uClibc snapshot version. arc uses its own uClibc
git tree, so this patch can be applied there if it's considered useful (adding
Mischa to Cc).
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
prev parent reply other threads:[~2014-01-13 8:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 6:26 [Buildroot] [PATCH v2 0/3] uclibc: build fixes for xtensa snapshot version Baruch Siach
2014-01-13 6:26 ` [Buildroot] [PATCH v2 1/3] uclibc: bump " Baruch Siach
2014-01-20 21:37 ` Peter Korsgaard
2014-01-13 6:26 ` [Buildroot] [PATCH v2 2/3] uclibc: xtensa: fix posix_spawn autoconf detection Baruch Siach
2014-01-15 13:31 ` Baruch Siach
2014-01-15 14:30 ` Peter Korsgaard
2014-01-13 6:26 ` [Buildroot] [PATCH v2 3/3] Revert "e2fsprogs: fix posix_fadvise() signature mismatch" Baruch Siach
2014-01-20 21:37 ` Peter Korsgaard
2014-01-13 8:13 ` [Buildroot] [PATCH v2 0/3] uclibc: build fixes for xtensa snapshot version Thomas Petazzoni
2014-01-13 8:23 ` Baruch Siach [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=20140113082338.GJ4944@tarshish \
--to=baruch@tkos.co.il \
--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.