On 9/20/10 3:14 PM, Felix Fietkau wrote:
Committed in r23104
- Felix
Thanks!
(wondering if I should have included -pipe as well... might make the compiles
go a little faster...)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http
Committed in r23104
- Felix
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
No other issues here (but then, I'm not an official reviewer).
On 9/20/10 1:25 PM, Roman Yeryomin wrote:
Sure, good idea!
Roman
On 20 September 2010 04:20, Philip Prindeville
wrote:
There are a lot of magic numbers in this code, like 64 and 16383 appearing
in several places.
Can they b
Sure, good idea!
Roman
On 20 September 2010 04:20, Philip Prindeville
wrote:
> There are a lot of magic numbers in this code, like 64 and 16383 appearing
> in several places.
>
> Can they be done as #define manifest constants instead?
>
> Or better yet, perhaps as const uint's so they're visibl
On 9/20/10 6:19 AM, RB wrote:
On Sun, Sep 19, 2010 at 23:03, Philip Prindeville
wrote:
What's involved in having a script (such as $topdir/localize) that can be
run after the system has been compiled and installed but before the actual
ext2 or squashfs images get cut?
Not a script, per se,
On Sun, Sep 19, 2010 at 23:03, Philip Prindeville
wrote:
> What's involved in having a script (such as $topdir/localize) that can be
> run after the system has been compiled and installed but before the actual
> ext2 or squashfs images get cut?
Not a script, per se, but any file/directory struct
Hi all,
I apologize for this dumb question, and it could have been ask million of
times (but I just can't find the right keywords to search for the right
answers)
I finally created my mesh network based on backfire. The MPs can ping each
other and see each other in "iw dev mesh station dump
