ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: David Howells <dhowells@redhat.com>
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
Date: Wed, 5 Sep 2018 21:33:36 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.YFH.7.76.1809052132190.15880@cbobk.fhfr.pm> (raw)
In-Reply-To: <17533.1536166384@warthog.procyon.org.uk>

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

  reply	other threads:[~2018-09-05 19:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05 16:53 David Howells
2018-09-05 19:33 ` Jiri Kosina [this message]
2018-09-05 19:51   ` Justin Forbes
2018-09-05 20:14   ` David Howells
2018-09-05 20:34     ` Justin Forbes
2018-09-05 20:53       ` Andy Lutomirski
2018-09-05 21:01         ` Justin Forbes
2018-09-06  6:53           ` joeyli
2018-09-06 10:00         ` Jani Nikula
2018-09-06 10:05         ` David Howells
2018-09-06 10:21           ` Jani Nikula
2018-09-07 19:53       ` Mauro Carvalho Chehab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=nycvar.YFH.7.76.1809052132190.15880@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=dhowells@redhat.com \
    --cc=jmforbes@linuxtx.org \
    --cc=joeyli.kernel@gmail.com \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=pjones@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox