[01:09] <mIKEjONE1> hey guys
[01:09] <mIKEjONE1> is there a way to build the kernel without having to build the whole thing from scratch everytime I make a change?
[01:09] <mIKEjONE1> I'm using fakeroot with debian/rules
[01:10] <mIKEjONE1> I'd like to have something that's able to only compile things that changed (i.e. the way Linux's Makefile works)
[01:32] <mIKEjONE1> it's getting kind of ridiculous, so any help would be greatly appreciated
[08:11] <apw> mIKEjONE1, yes after build if you want to change a few files and rebuild you can remove debian/stamp/stamp-build-<flavour> and then re-run fakeroot debian/rules binary-generic
[13:49] <rtg> henrix, kamal: I just sent a patch to the k-team list in reference to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1397976/comments/4 - that commit looks good for stable.
[13:52] <henrix> rtg: yep, looks like it could be applied to 3.13 kernel (all others seem to have it already)
[13:52] <rtg> henrix, clean cherry-pick
[13:53] <henrix> rtg: cool, thanks.  kamal, i guess you can pick it ;-)
[13:54] <rtg> henrix, it might be a bit early for California slackers :)
[13:54] <henrix> heh, indeed
[13:54] <apw> henrix, so did we have that in P and fail to apply it to T somehow ?
[13:56] <henrix> apw: no, i we don't have it P but i believe it is not applicable to such an old kernel...
[13:56]  * henrix goes check
[13:56] <apw> henrix, ahh ok, it was the regression word that confused me
[13:58] <henrix> apw: right, so the issue was introduced by commit eafbe67f8476 ("n_tty: Refactor input_available_p() by call site"), which was cherry-picked into trusty.  so it *may* not even be applicable to stable 3.13, depending on whether or not it contains this commit
[13:59] <henrix> kamal: ^
[15:03] <jsalisbury> **
[15:03] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[15:03] <jsalisbury> **
[16:22] <kamal> rtg, apw, henrix: fyi, 3.13-stable does not contain eafbe67 "n_tty: Refactor input_available_p() by call site", so I'll take no action on that topic, barring further discussion.
[16:27] <henrix> kamal: ack
[16:55] <jsalisbury> ##
[16:55] <jsalisbury> ## Kernel team meeting in 5 minutes
[16:55] <jsalisbury> ##
[16:56] <bkero> Can I ask that someone install libssl-dev to the kernel build hosts so that we can actually generate kernel packages? http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.3-rc1-unstable/
[16:57] <bkero> Is that off-topic for the meeting?
[20:24] <hallyn> what is all this:
[20:24] <hallyn> root     22390     2  0 15:23 ?        00:00:00 [kworker/u16:88]
[20:26] <bkero> a kernel worker process
[20:28] <hallyn> why so many of them?
[20:28] <hallyn> (this is appears to be new)
[20:29] <hallyn> oh, actually they've died down
[20:29] <hallyn> perhaps a side-effect of resume.  interesting
[20:29] <bkero> It's a kernel thing
[20:29] <bkero> check out the kernel docs
[20:36] <rharper> is there any place to get previously published but superceeded kernels?  I've got an issue on the latest vivid kernel but works fine on the vivid released kernel;  would like to bisect but without building all of those kernels 
[20:37] <sforshee> hallyn: entirely possible it was a result of resume, if that generated a lot of workqueue items. I think the kernel scales the number of worker threads.
[20:39] <sforshee> rharper: aren't they all still in the archive?
[20:40] <rharper> did a apt-cache policy linux-image-generic and only showed the latest; so I probably need some apt-fu to find it
[20:43] <sforshee> linux-image-generic is a meta package. Every new kernel version is its own package so that multiple kernels can be installed at the same time.
[20:44] <rharper> ah, ok
[20:44] <rharper> cool; I think I can get them now
[20:44] <rharper> sforshee: thanks
[20:44] <sforshee> np