**** BEGIN LOGGING AT Fri Aug 30 02:59:58 2013 Aug 30 04:47:29 build #244 of octeon is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/octeon/builds/244 Aug 30 06:53:12 swalker: I'm one of the upstream developers of reSIProcate, so yes, I would be helping to maintain the asio and reSIProcate stuff in OpenWRT Aug 30 07:31:32 stintel: moving the antennas further apart could indeed help Aug 30 11:12:42 <__trine> -j3 Aug 30 11:28:38 ping rundfreifunk Aug 30 11:29:31 hey Aug 30 11:29:36 -> private Aug 30 11:46:56 luka hi, do you have a few minutes or do you prefer I reply your e-mail? I'm the flashchip patch guy you just replied :) Aug 30 12:41:23 Devastator: pong Aug 30 12:48:06 luka hi, so, I've already send to linux-mtd, but I was hoping to get this patch as platform/generic and when it gets kernel upstream, we can drop it, how that sounds? Aug 30 12:49:01 which board needs the patch Aug 30 12:50:03 D-Link DIR-610 A1, ralink soc Aug 30 12:50:37 is it in openwrt? Aug 30 12:51:31 yes, I'm porting the device and 99% was already pushed upstream Aug 30 12:52:32 this patch was missing from my series, I'm still learning how to work with patches, sorry Aug 30 12:52:50 so is that the last patch that is missing? Aug 30 12:54:00 yes, how can I tell to push to platform/generic? Aug 30 12:55:08 assuming it's the right thing to do, of course.. Aug 30 12:57:13 Devastator: please resend a patch with commit message that was sent to the linux-mtd mailing list Aug 30 12:57:44 Devastator: also give links to the proposed patch on mailing list and patchwork Aug 30 12:58:01 i would like to see something like this: https://dev.openwrt.org/browser/trunk/target/linux/generic/patches-3.10/470-mtd_m25p80_add_pm25_flash_support.patch Aug 30 13:02:11 ok, by links you mean a forum topic or the datasheet link is enough? I will explain better why this patch is needed on v2 Aug 30 13:02:24 the datasheet is all I have so far.. Aug 30 13:02:46 by links i mean the links to linux-mtd patchwork and mailing list where the patch was sent Aug 30 13:03:45 thanks, now I understand Aug 30 13:04:46 i'd like to have more documentation about the patches we have in generic, that is why i'm asking you for this Aug 30 13:05:23 also, with the links it's easy to see what is the situation in the upstream (if patch was rejected for example) Aug 30 13:09:06 luka sure, I don't mind, I want to do things right, but keep in mind I may ask a lot heheh not too experienced as you noticed Aug 30 13:09:42 no problem Aug 30 13:11:44 luka basically this? http://patchwork.ozlabs.org/patch/271263/ and http://lists.infradead.org/pipermail/linux-mtd/2013-August/048449.html Aug 30 13:13:09 yes, but you should't have sent it as RFC also the comment "I hope this patch is in proper format and my mail client didn't mess it." should not be included in commit message Aug 30 13:14:31 Devastator: please setup properly git send-email and you will be able to send patches just fine Aug 30 13:14:41 you can test it by sending patches to yourself first Aug 30 13:16:05 luka are my patches showing correctly to you? I was using imap-send, I don't trust my mail client at all! Aug 30 13:16:56 i didnt try to apply them Aug 30 13:17:13 you can download the patch from patchwork and try if it's working... Aug 30 13:18:11 also, I wasn't sure about the patch, that's why I add [RFC], Jonas told me to use it when I wanted comments before a final version Aug 30 13:18:29 I fail to use best practices I suppose heheh Aug 30 13:19:12 well, i want to wait what linux-mtd will say... Aug 30 13:20:23 me too, I think they will scream at me anyway hehe Aug 30 13:21:09 but I promise to pay attention for the next ones Aug 30 13:21:56 which mail client do you use? Aug 30 13:24:31 mutt, but i send patches using git send-email Aug 30 13:28:25 yep, imap-send is pointless without ssl support, most isp imap requires ssl nowadays Aug 30 13:47:18 Devastator: also it seems your mail client converted the tabs to (single) spaces Aug 30 13:50:07 nice.. Aug 30 13:51:35 man, you don't know how this pisses me off, I've read tons of guides on how to properly setup this mail client and again, it screws my patches Aug 30 13:51:52 which will be rejected by linux-mtd.. Aug 30 13:56:40 <[florian]> why don't you use git-send-email? Aug 30 13:58:11 and bypass this friggin' client, it worked in the past I guess Aug 30 14:05:39 cyrusff: I think something weird is going on with odhcp6c Aug 30 14:06:00 cyrusff: my PD lease changed again, even though I didn't "ifdown wan6" at all Aug 30 14:06:25 cyrusff: and according to the CMTS, I have now 2 PD leases assigned Aug 30 14:06:55 (I checked with the guy at my ISP that is handling the v6 rollout) Aug 30 14:08:57 KanjiMonster can I make a test by sending to you with send-email? if you don't mind.. I bet my client will replace tabs with single space, so I can't check myself Aug 30 14:21:10 Devastator: you can, but I can't promise a timely response - I'm at work after all ;) Aug 30 14:21:39 sure, I am too Aug 30 14:23:00 cyrusff: I am going to post some details via /q Aug 30 14:31:18 KanjiMonster sent to jogo@... I really hope it is fine this time Aug 30 14:31:57 stintel: seems the duplicate address detection is going nuts for whatever reason Aug 30 14:37:29 cyrusff: just noticed in the CMTS that a friend (who I told to run BB as well) also has 2 active leases, like me Aug 30 14:37:42 cyrusff: I asked him to logread | grep dup Aug 30 14:38:01 yeah i've seen the DAD going nuts for a few people now Aug 30 14:38:13 the problem is that the linux kernel is slightly broken there Aug 30 14:38:20 hmm Aug 30 14:38:25 i will remove the DAD for now Aug 30 14:38:43 and will reimplement it later in another way Aug 30 14:41:02 Devastator: I did not receive any emails yet on my openwrt.org account Aug 30 14:41:31 stintel: i removed it upstream, git hash is "dfc86766bf0b3d28f55adf5deb340b1d40176808" Aug 30 14:41:37 if you like to rebuild Aug 30 14:42:07 cyrusff: ok. here at my ISP we started using a WNDR3700v2 with BB snapshot today, we'll keep an eye on it if it will do the same on that one Aug 30 14:42:09 don't have time to build, test and update the openwrt Makefile right now Aug 30 14:42:18 cyrusff: np, I'll give it a shot Aug 30 14:42:21 ok thx Aug 30 14:42:27 cyrusff: what my colleague also mentioned Aug 30 14:42:45 the client should send a DECLINE for the IANA only Aug 30 14:42:54 but I suspect it also does it for the IAPD ? Aug 30 14:43:03 i guess it includes the PD as well Aug 30 14:43:11 although thats incorrect yeah Aug 30 14:43:20 anyway, the DECLINE is not really that important right now Aug 30 14:43:26 so I rather remove it if it breaks Aug 30 14:44:00 i will hopefully start doing the next ipv6 iteration in a few weeks Aug 30 14:46:04 ok, I'll build with that git hash and follow up a little Aug 30 14:46:40 gonna try and release this x:x:x:0100::/56 and get the 0000::/56 back ;) Aug 30 14:51:05 Devastator: looks better Aug 30 14:52:43 KanjiMonster any other tips? or should I just wait for it get rejected by linux-mtd and send v2 this way? Aug 30 14:58:46 Devastator: I haven't tried to apply it, but it looks as if it should. And regarding v2; if checkpatch doesn't complain, you can probably just send a v2 directly, no need to wait for it to get rejected - this might take several days Aug 30 14:59:57 KanjiMonster is checkpatch, checkpatch.pl? thanks for your tips Aug 30 15:00:52 yes Aug 30 15:01:19 will do Aug 30 15:08:58 cyrusff: ok, I released the 2nd lease and then got the first one back, now running with dfc86766bf0b3d28f55adf5deb340b1d40176808 and norelease 1. now I should really keep that PD :) Aug 30 15:09:11 stintel: yay ;) Aug 30 15:09:16 thanks again for quick response Aug 30 15:09:31 sure, np Aug 30 15:11:37 pretty handy that I am working at my ISP during the IPv6 rollout :) Aug 30 15:12:12 hehe Aug 30 15:13:41 luka: yea or nay? http://patchwork.openwrt.org/patch/3966/ Aug 30 15:13:42 luka: it's in mainline now: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/net/usb/hso.c Aug 30 15:22:46 DonkeyHotei: i dont think that needs to be pulled in generic patches, but if somebody else decides to do it that is fine with me Aug 30 15:23:44 luka: it would affect multiple targets Aug 30 15:29:58 i didn't say it wouldn't, i just dont think it's that important Aug 30 15:32:50 blogic: received the devices yet? Aug 30 15:39:15 luka: it's important for any device used for 3g connections Aug 30 16:20:03 KanjiMonster whenever you can, check this approach, the first lines are checkpatch output: http://codepad.org/lPnMfYNf Aug 30 18:13:39 build #334 of rb532 is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/rb532/builds/334 Aug 30 18:16:13 build #334 of ppc44x is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/ppc44x/builds/334 Aug 30 20:52:25 build #366 of orion is complete: Failure [failed compile_8] Build details are at http://buildbot.openwrt.org:8010/builders/orion/builds/366 Aug 30 20:54:58 build #316 of sibyte is complete: Failure [failed shell_12] Build details are at http://buildbot.openwrt.org:8010/builders/sibyte/builds/316 Aug 30 21:13:29 build #347 of uml is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/uml/builds/347 Aug 30 23:05:48 build #326 of avr32 is complete: Failure [failed compile_5] Build details are at http://buildbot.openwrt.org:8010/builders/avr32/builds/326 **** ENDING LOGGING AT Sat Aug 31 02:59:58 2013