From: Jon Masters <jcm@redhat.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: Date/Time?
Date: Mon, 21 May 2018 15:16:56 -0400 [thread overview]
Message-ID: <abac87bd-e90e-4f7b-4962-b624c7bc4251@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1805212054520.1599@nanos.tec.linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1097 bytes --]
On 05/21/2018 02:56 PM, speck for Thomas Gleixner wrote:
> On Mon, 21 May 2018, speck for Jon Masters wrote:
>> One of the problems does seem to be that we didn't have a dedicated list
>> for v4 earlier. I think it's important to tackle that next time around.
>
> Crap. What's important is that _WE_ can decide and act on our own without
> having to ask Intel about every fart.
Sure. My point is Intel didn't own v4. GPZ own that one. Intel just took
point in doing disclosures to various folks once again. I actually
consider what they are trying to do to be quite noble in intention, but
(as I have said to Intel's execs with all due intended respect) it's not
their place to do this for the whole industry. And it's important to
understand the separation between v4 and any other past/future issue.
This is why we need a better framework (and some folks are working on
something) for joint industry issues that removes single vendors from
owning architectural embargoes that impact multiple others.
Jon.
--
Computer Architect | Sent from my Fedora powered laptop
next prev parent reply other threads:[~2018-05-21 19:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-19 17:26 [MODERATED] Date/Time? Greg KH
2018-05-19 17:51 ` [MODERATED] Date/Time? Borislav Petkov
2018-05-19 18:45 ` Linus Torvalds
2018-05-19 19:07 ` [MODERATED] " Borislav Petkov
2018-05-19 19:48 ` Linus Torvalds
2018-05-19 20:22 ` [MODERATED] " Borislav Petkov
2018-05-20 20:58 ` Jon Masters
2018-05-19 18:21 ` David Woodhouse
2018-05-19 19:05 ` Greg KH
2018-05-20 19:23 ` David Woodhouse
2018-05-20 23:01 ` David Woodhouse
2018-05-21 8:35 ` Greg KH
2018-05-20 17:45 ` Jiri Kosina
2018-05-20 18:19 ` Greg KH
2018-05-20 18:35 ` Borislav Petkov
2018-05-20 19:57 ` Greg KH
2018-05-20 18:36 ` Linus Torvalds
2018-05-20 18:48 ` Jiri Kosina
2018-05-20 20:59 ` Jon Masters
2018-05-20 21:09 ` Jiri Kosina
2018-05-21 6:11 ` Greg KH
2018-05-20 21:48 ` Linus Torvalds
2018-05-20 21:56 ` David Woodhouse
2018-05-21 6:16 ` Greg KH
2018-05-21 7:18 ` David Woodhouse
2018-05-21 15:23 ` Date/Time? Thomas Gleixner
2018-05-21 16:46 ` [MODERATED] Date/Time? Greg KH
2018-05-21 17:12 ` Konrad Rzeszutek Wilk
2018-05-21 19:42 ` Greg KH
2018-05-21 19:48 ` Jiri Kosina
2018-05-21 20:30 ` Jon Masters
2018-05-22 8:00 ` Peter Zijlstra
2018-05-22 9:26 ` Greg KH
2018-05-22 16:32 ` Andi Kleen
2018-05-23 14:15 ` Jon Masters
2018-05-21 17:22 ` Jon Masters
2018-05-21 18:56 ` Date/Time? Thomas Gleixner
2018-05-21 19:16 ` Jon Masters [this message]
2018-05-21 20:43 ` [MODERATED] Date/Time? Greg KH
2018-05-21 17:31 ` Jon Masters
2018-05-21 18:53 ` Date/Time? Thomas Gleixner
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=abac87bd-e90e-4f7b-4962-b624c7bc4251@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.