From: Jon Masters <jcm@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: Dates again..?
Date: Thu, 5 Jul 2018 14:57:32 -0400 [thread overview]
Message-ID: <8506945f-5aa8-7534-0daf-1a899ff95335@redhat.com> (raw)
In-Reply-To: <4d7a768f-912b-c8fc-de27-8f3e3824ac77@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]
On 07/05/2018 02:42 PM, speck for Andrew Cooper wrote:
> On 05/07/18 19:40, speck for Jon Masters wrote:
>> On 07/04/2018 12:52 PM, speck for Andrew Cooper wrote:
>>> On 04/07/18 17:50, speck for Linus Torvalds wrote:
>>>> One of the downsides of this encrypted mailing list is that none of my
>>>> usual email search tools work with it. So now I can't find the dates. It
>>>> doesn't help that they keep changing, and there are several different
>>>> issues.
>>>>
>>>> I know July 10th was _one_ date at one point. "Spectre v1, electric
>>>> boogaloo: the store edition"?
>>> Correct.
>>>
>>>> And L1TF was later still. August?
>>> August 14th.
>> Andrew is, as usual, correct.
>>
>>>> What else?
>>> TLBleed "some time soon".
>> I've asked Ben for a specific date. He's currently in the UK and meeting
>> with a few folks to discuss TLBleed. I hooked him up with a visit to Arm
>> Cambridge earlier today and the feedback was positive. Will get you a
>> specific date before the end of the week (I hope).
>>
>>> NetSpectre 27th July.
>>>
>>> Those are the only remaining issues which come to mind.
>> There are additional topics which cause me to believe this list should
>> remain in place for the remainder of the year. Just an FYI.
>
> Well - you couldn't possibly speculate, could you ;)
Looking forward to in-order retirement.
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2018-07-05 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 16:50 [MODERATED] Dates again..? Linus Torvalds
2018-07-04 16:52 ` [MODERATED] " Andrew Cooper
2018-07-05 18:40 ` Jon Masters
2018-07-05 18:42 ` Andrew Cooper
2018-07-05 18:57 ` Jon Masters [this message]
2018-07-05 20:06 ` Jon Masters
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=8506945f-5aa8-7534-0daf-1a899ff95335@redhat.com \
--to=jcm@redhat.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).