**** BEGIN LOGGING AT Wed Nov 16 02:59:57 2011
Nov 16 22:10:54 <ant____> bluelightning: what about the steps to commit 3.1? I'd remove 2.6.39 and .git.
Nov 16 22:11:36 <bluelightning> ant____: presumably JaMa is ok with removing the git recipe? I think it was him who submitted the patch to add it
Nov 16 22:12:09 <ant____> yes, he insistds doing that now and then (only for spitz). Dunno why...he's not doing any kernel work/testing...
Nov 16 22:13:18 <ant____> if you mind we can ask him, or better, I'll submit the remove-patch to ml
Nov 16 22:13:40 <ant____> my point is about reordering /kernel a bit
Nov 16 22:14:01 <bluelightning> yeah I'd say submit the patch and if he disagrees he can reply
Nov 16 22:14:26 <ant____> and about hx4700 I'd move it to 3.1.1
Nov 16 22:15:33 <bluelightning> yeah let's go with that also
Nov 16 22:16:20 <ant____> ok, I'll split the patches then
Nov 16 22:16:32 <bluelightning> thanks
Nov 16 22:16:48 <ant____> ah, wait, maybe I'll bake a collie-kernel before....
Nov 16 22:17:08 <bluelightning> btw JaMa's onlike atm
Nov 16 22:20:39 <ant____> now I'm tempted to use COMPATIBLE_MACHINE instead of DEFAULT_PREFERENCE
Nov 16 22:20:58 <ant____> for linux_3.1
Nov 16 22:21:25 <ant____> how does that behave crossing layers?
Nov 16 22:21:55 <ant____> I remember using Angstrom scripts some ti kernel was appearing
Nov 16 22:22:05 <ant____> from their layer
Nov 16 22:22:06 <bluelightning> ant____: should be OK, assuming something else provides what's needed
Nov 16 22:22:58 <ant____> well, or the opposite, foreign kernels sneaking in
Nov 16 22:23:16 <ant____> maybe was just a bad recipe
Nov 16 23:05:42 <ant____> hm..I seee we have the h1940 in 2.6.39
Nov 16 23:06:09 <ant____> what to do with that two ipaqs? Any maintainer?
Nov 16 23:11:38 <bluelightning> ant____: h1940 kernel is maintained by anarsoul
Nov 16 23:11:50 <bluelightning> it's all in mainline though so in theory it should be fine to upgrade
Nov 16 23:12:01 <bluelightning> I should really test it though... hmm
Nov 16 23:12:09 <ant____> yes, I don't see patches for that one
Nov 16 23:13:07 <ant____> ok, ideally I'll have to refresh and shrink both ipaq's defconfig
Nov 16 23:13:26 <ant____> so I'll see if the hx4700 patches do apply
Nov 16 23:13:57 <ant____> it will take a while but is worth: we could unify with one single recipe
Nov 16 23:14:16 <ant____> btw, PR is needed or can we live without now?
Nov 16 23:15:52 <bluelightning> PR = "r0" for a new version surely?
Nov 17 00:11:34 <ant____> well, linux.inc has any
Nov 17 00:11:50 <ant____> we have linux-kexecboot with inc_pr though
Nov 17 00:12:15 <ant____> I'd like to standardize...
Nov 17 00:12:43 <ant____> in fact the PR should be increased once a new kexecboot release peeks out
Nov 17 00:13:01 <ant____> maybe the we could embed kexecboot version/tag in the PR
Nov 17 00:13:15 <ant____> this would be much clearer
Nov 17 00:15:44 <ant____> I'll think about that
Nov 17 00:15:46 <ant____> gn
**** ENDING LOGGING AT Thu Nov 17 02:59:57 2011