[18:30] <xnox> apw, do we still need kmod, if we have systemd-modules-load thing?
[18:31]  * xnox wonders if the systemd-modules-load actually masks kmod already
[18:32] <xnox> ah it does, via systemd. It ships kmod.service -> systemd-modules-load.service symlink
[19:41] <tyhicks> if I'm doing artful backports of some patches that were recently acked upstream to land in 4.14, what git tree/branch should I be targeting? the master branch of the unstable tree?
[20:09] <sforshee> tyhicks: that or artful/master-next, whichever is more convienient for you
[20:10] <sforshee> if it only applies to one or the other and I can't figure out how to reconcile it, then I'll ask you to provide it for the other one ;-)
[20:10] <sforshee> or if they are in linux-next already you can just give me the sha1's and I can cherry pick them directly
[20:11] <tyhicks> I think it'll apply cleanly to 4.13 and will need a little work to 4.12 so I'll do the backport to artful/master-next and then reference the sha1's from linux-next for unstable/master-next
[20:12] <sforshee> wfm
[20:15] <sforshee> jjohansen: do you have an ETA for apparmor sauce for 4.13?
[20:19] <jjohansen> sforshee: my 4.14 pull request is going out this week, so I should be able to get you it by the end of week
[20:20] <jjohansen> there will be a couple of patches that are in revision and are targeted to 4.15 that we will probably get some revision, but we can revert and apply newer iterations as needed
[20:22] <sforshee> jjohansen: sounds great, thanks