From: Greg KH <gregkh@linuxfoundation.org>
To: speck@linutronix.de
Subject: [MODERATED] Re: LVI
Date: Wed, 20 Nov 2019 18:46:36 +0100 [thread overview]
Message-ID: <20191120174636.GA3074978@kroah.com> (raw)
In-Reply-To: <61d8de91-f0a2-868b-a747-42a24a5ba110@citrix.com>
On Wed, Nov 20, 2019 at 05:30:02PM +0000, speck for Andrew Cooper wrote:
> On 20/11/2019 17:25, speck for Greg KH wrote:
> > On Wed, Nov 20, 2019 at 11:13:53AM -0600, speck for Josh Poimboeuf wrote:
> >> On Tue, Nov 19, 2019 at 11:40:08AM -0600, speck for Josh Poimboeuf wrote:
> >>> Hi,
> >>>
> >>> What kernel changes (if any) are needed for LVI? I haven't seen any
> >>> discussion here.
> >>>
> >>> The last I heard, the official CRD was Dec 10, but was likely to move to
> >>> March.
> >> Luckily this has been moved to March 10, 2020.
> > It has?
>
> Yes, on the call which ended half an hour ago.
>
> > Where is this all being tracked?
> >
> > Last I saw was a strange presentation with odd dates, can't we have a
> > "simple" text file in keybase at the very least for this type of thing?
>
> There is. Look at the keybase git repo. If things are set up suitably,
>
> git clone keybase://team/vulnresearch.2h_2019/vulnresearch.2h_2019
>
> authorized_issues.tsv is already up to date.
Ok, nice, _now_ it is, nothing like documenting after-the-fact :)
Anyway, why did it move? And what is the status of patches from Intel
for this?
thanks,
greg k-h
next prev parent reply other threads:[~2019-11-20 17:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 17:40 [MODERATED] LVI Josh Poimboeuf
2019-11-19 17:51 ` [MODERATED] LVI Andrew Cooper
2019-11-19 18:27 ` Josh Poimboeuf
2019-11-19 19:26 ` Andrew Cooper
2019-11-20 9:52 ` Paolo Bonzini
2019-11-19 18:12 ` Greg KH
2019-11-19 18:21 ` Josh Poimboeuf
2019-11-19 18:46 ` Greg KH
2019-11-19 18:21 ` Paolo Bonzini
2019-11-19 18:22 ` Andrew Cooper
2019-11-19 18:27 ` Josh Poimboeuf
2019-11-19 18:36 ` Luck, Tony
2019-11-20 17:02 ` Greg KH
2019-11-19 18:39 ` Andrew Cooper
2019-11-19 21:00 ` Josh Poimboeuf
2019-11-19 21:03 ` Josh Poimboeuf
2019-11-20 14:11 ` Andrew Cooper
2019-11-20 8:04 ` Peter Zijlstra
2019-11-20 9:49 ` Andrew Cooper
2019-11-20 17:13 ` Josh Poimboeuf
2019-11-20 17:25 ` Greg KH
2019-11-20 17:29 ` Tyler Hicks
2019-11-20 17:30 ` Andrew Cooper
2019-11-20 17:46 ` Greg KH [this message]
2019-11-20 19:09 ` Peter Zijlstra
2019-11-20 19:19 ` Greg KH
2019-11-21 0:50 ` LVI Thomas Gleixner
2019-11-21 13:45 ` [MODERATED] LVI Greg KH
2019-11-26 0:54 ` Andi Kleen
2019-11-26 10:37 ` Greg KH
2019-11-26 18:23 ` Andi Kleen
2019-11-27 7:38 ` Greg KH
2019-11-26 10:55 ` Paolo Bonzini
2019-11-26 18:28 ` Andi Kleen
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=20191120174636.GA3074978@kroah.com \
--to=gregkh@linuxfoundation.org \
--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 NNTP newsgroup(s).