From: Jiri Kosina <jkosina@suse.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v6] boot-time control
Date: Fri, 6 Jul 2018 21:23:57 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.1807062118420.997@cbobk.fhfr.pm> (raw)
In-Reply-To: <20180706191027.GH25550@tassilo.jf.intel.com>
On Fri, 6 Jul 2018, speck for Andi Kleen wrote:
> This should refer to the Document I posted yesterday (which should be
> also merged into the patchkit)
>
> Also probably should not refer the CVE, it is usually not that useful.
I don't know ... I'd bet the number of sysadmins who are able to look up a
CVE is probably much higher than number of sysadmins capable/willing to
wander through kernel sources to find information.
What would be your suggested wording so that it's digestible by a sysadmin
who's never seen a kernel source tree before? There are tons of those
guys.
Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2018-07-06 19:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-06 18:47 [MODERATED] [PATCH v6] boot-time control Jiri Kosina
2018-07-06 19:10 ` [MODERATED] " Andi Kleen
2018-07-06 19:23 ` Jiri Kosina [this message]
2018-07-06 19:39 ` Thomas Gleixner
2018-07-06 20:06 ` [MODERATED] " Luck, Tony
2018-07-06 20:19 ` Jiri Kosina
2018-07-06 20:31 ` Josh Poimboeuf
2018-07-06 20:01 ` Josh Poimboeuf
2018-07-08 12:42 ` Thomas Gleixner
2018-07-08 13:13 ` [MODERATED] " Jiri Kosina
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.1807062118420.997@cbobk.fhfr.pm \
--to=jkosina@suse.com \
--cc=speck@linutronix.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).