[14:04] <cyphermox> ogasawara: hi; did the security team review and OK linux-aws for main yet?
[14:05] <cyphermox> (I'm doing the MIR review)
[14:05] <ogasawara> cyphermox: I know we were discussing with them about it moving to Main, but I don't know if they have actually done the review.
[14:05] <ogasawara> tyhicks: ^^
[14:07] <ogasawara> I'm hopeful that the review should be relatively straight forward since it's based on the stock xenial distro kernel
[14:07] <cyphermox> right
[14:18] <tyhicks> ogasawara, cyphermox: hey - we haven't done a review yet
[14:19] <tyhicks> ogasawara, cyphermox: like you mentioned, we're not going to do any sort of in depth review
[14:19] <cyphermox> tyhicks: I'm not looking for an in-depth review necessarily, but at least acknowledgement that this is ok as a MIR
[14:20] <cyphermox> rubber-stamping if that's what you want to do is fine by me, as long as somebody has looked at the bug
[14:20] <cyphermox> https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1672850
[14:20] <tyhicks> cyphermox: it is ok as a MIR - we have full confidence in the kernel team more than capably supporting the package
[14:20] <cyphermox> :)
[14:21] <tyhicks> ack from security
[14:21] <cyphermox> ogasawara: so all that is missing is a team subscriber I think, for linux-aws bugs
[14:22] <ogasawara> cyphermox: oh, that should be ~canonical-kernel-team, I can get that done
[14:24] <apw> ogasawara, actually i don't think we use that one for that, there is another one
[14:24] <ogasawara> apw: ah, ok, /me waits
[14:25] <apw> i am sure slangasek added them to the right one last time, now what am i thinking of
[14:26] <apw> ogasawara, i think it is ~kernel-packages
[14:27] <apw> ogasawara, which you are a member of :)
[14:28] <apw> ogasawara, yeah that is the one ... it is intended to stop us getting deluged with spam
[14:29] <ogasawara> apw: hrm, I do not see ~kernel-packages listed as an option for me to select in the drop down of teams I administer to subscribe to linux-aws
[14:29] <apw> oh you have to 
[14:29] <apw> be an admin do you, asses
[14:30] <apw> bdmurray, hey ... kernel-packages, that is the launchpad group for package "we" support right?  but we cannot use it as only an admin can subscribe it
[14:30] <cyphermox> ahah oops.
[14:30] <apw> (and that is you if that isn't clear :))
[14:31] <apw> yeah, derp.  likely ~leannogasawara at least should be that
[14:40] <leitao> rtg, Can you check if my emails to kernel-team were moderated again?
[14:41] <leitao> I sent them from the subscribed email this time
[14:42] <leitao> I do not see them at https://lists.ubuntu.com/archives/kernel-team/2017-March/thread.html
[15:01] <rtg> leitao, you mean this set ? https://lists.ubuntu.com/archives/kernel-team/2017-March/083147.html
[15:02] <leitao> rtg, yes. Thanks!
[15:02] <rtg> leitao, they came throug unmoderated
[15:02] <leitao> weird, but this set does not show up at https://lists.ubuntu.com/archives/kernel-team/2017-March/thread.html
[15:02] <rtg> through*
[15:03] <leitao> rtg, nm
[15:03] <apw> leitao, does for me ... next to last thread
[15:03] <leitao> i need more coffee
[15:03] <rtg> refresh ?
[15:03] <leitao> rtg, I was looking at the top of the page.
[15:03] <leitao> we are good, sorry for the noise
[15:03] <apw> heh, i was about to say the page is in a counter-intuitive order
[15:04] <leitao> apw, yes, All the archives I read are sorted reversely 
[15:11] <ogasawara> cyphermox: ok, ~kernel-packages is now subscribed
[15:12] <ogasawara> thanks to apw
[15:12] <ogasawara> bdmurray: nothing to do here now
[15:12] <apw> ogasawara, heh it was him who clued me in, so thanks go to him
[15:13] <bdmurray> ogasawara: sheesh, way to just dismiss me
[15:13] <ogasawara> :)
[15:13] <bdmurray> ogasawara: I'm glad I'm not on your team
[15:14] <ogasawara> bdmurray: well, I don't want you injuring yourself even more, not after that nasty fall off the cliff
[15:14] <bdmurray> lol
[22:24] <leitao> rtg, I found an easy way to cherry pick those patches for #1675806. It is not a clean way, tho
[22:25] <leitao> reverting ba46da7c1cc57d83f6af66bfe8f10516151c7923 and applying the KVM patchset, and then reapplying it (ba46da7c1cc57d83f6af66bfe8f10516151c7923)
[22:25] <leitao> This solve most of the problems.
[22:25] <leitao> anyway, I will try to create a clean tree next week.