From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 9CE22BC4 for ; Wed, 5 Sep 2018 19:33:40 +0000 (UTC) Received: from mx1.suse.de (mx2.suse.de [195.135.220.15]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 330C57CF for ; Wed, 5 Sep 2018 19:33:40 +0000 (UTC) Date: Wed, 5 Sep 2018 21:33:36 +0200 (CEST) From: Jiri Kosina To: David Howells In-Reply-To: <17533.1536166384@warthog.procyon.org.uk> Message-ID: References: <17533.1536166384@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: James.Bottomley@HansenPartnership.com, pjones@redhat.com, jmforbes@linuxtx.org, joeyli.kernel@gmail.com, ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [TECH TOPIC] Kernel lockdown and secure boot List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 5 Sep 2018, David Howells wrote: > I would like to suggest having a kernel summit session on how to > progress the secure boot and kernel lockdown patches. AIUI, various > distributions are actually including them in their kernels. FWIW, it's one of the rare exceptions where we are carrying non-upstream patchset in our tree, yes. I have to admit I already forgot what exactly was actually blocking the upstream merge ... ? Thanks, -- Jiri Kosina SUSE Labs