Re: [OpenWrt-Devel] toolchain: introducing gcc 4.4.5 with Linaro enhancements

2010-11-22 Thread Imre Kaloz
Hi, On Sun, 21 Nov 2010 12:37:37 +0100, Marcus Osdoba wrote: Currently I'm working on improved dockstar support for OpenWrt. The current toolchain 4.3.3+cs is not that up to date and linaro 4.5 branch is already included. Unfortunatly, this version does not support Marvell Feroceon (mtune=mar

Re: [OpenWrt-Devel] [PATCH] iptables compile fix

2010-11-22 Thread Bas Mevissen
On Mon, 22 Nov 2010 11:51:22 +0100, Maarten Bezemer wrote: > Gr... Whatever I try it compiles now (even my own .config works)... > Weird since there is nothing changed to the iptables package lately (or > related things?). > > Only change I can think of is the update to Kubuntu 10.10 (from 10.04)

[OpenWrt-Devel] Compile fix for r24041

2010-11-22 Thread Joerg Dorchain
Hello, the following patches points to a compilation problem with svn revision r24041 and gives one possible solution. Bye, Joerg Index: package/mac80211/patches/800-b43-gpio-mask-module-option.patch === --- package/mac80211/patche

Re: [OpenWrt-Devel] [PATCH] iptables compile fix

2010-11-22 Thread Maarten Bezemer
Gr... Whatever I try it compiles now (even my own .config works)... Weird since there is nothing changed to the iptables package lately (or related things?). Only change I can think of is the update to Kubuntu 10.10 (from 10.04), but that was a while ago as well. Unfortunately I do not have a 10.0

Re: [OpenWrt-Devel] [PATCH] triggerhappy: update to 0.1.6

2010-11-22 Thread Jonas Gorski
On 22 November 2010 09:41, Matthias Buecher / Germany wrote: > On 22.11.2010 09:35, Stefan Tomanek wrote: > As far as I know your setup shouldn't mangle the patch. > Can someone confirm? The patch looks fine for me ("show original" in GMail shows it with tabs where appropriate).

Re: [OpenWrt-Devel] [PATCH] triggerhappy: update to 0.1.6

2010-11-22 Thread Matthias Buecher / Germany
On 22.11.2010 09:35, Stefan Tomanek wrote: > Dies schrieb Matthias Buecher / Germany (m...@maddes.net): > >> So if you are sure that the patch is not mangled by your mail client (no >> wraps, no tabs to spaces), then inline is definitely preferred. >> Maybe setting some options in your mail client

Re: [OpenWrt-Devel] [PATCH] triggerhappy: update to 0.1.6

2010-11-22 Thread Stefan Tomanek
Dies schrieb Matthias Buecher / Germany (m...@maddes.net): > So if you are sure that the patch is not mangled by your mail client (no > wraps, no tabs to spaces), then inline is definitely preferred. > Maybe setting some options in your mail client will avoid this behaviour. Can you point me to t

Re: [OpenWrt-Devel] [PATCH] triggerhappy: update to 0.1.6

2010-11-22 Thread Matthias Buecher / Germany
Inline is better for commenting the patch, as the comment can be placed directly at the discussed location. But a mangled patch is hard to apply. If it is attached it normally doesn't get mangled, but then commenting is harder as the relevant code is not shown. So if you are sure that the patch i