All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: Re: Date/Time?
Date: Mon, 21 May 2018 17:23:51 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.21.1805211647240.1599@nanos.tec.linutronix.de> (raw)
In-Reply-To: <1526887128.8186.25.camel@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 2138 bytes --]

On Mon, 21 May 2018, speck for David Woodhouse wrote:
> On Mon, 2018-05-21 at 08:16 +0200, speck for Greg KH wrote:
> 
> > And I doubt we need another git tree, we already have one, that should
> > have worked for any arch that needed it.  The problem seems to be that
> > those developers were not "allowed" here for us to work together,
> > exactly like last time.
> 
> If that is 100% known to be the case, then it should be part of our
> messaging when we release.

We could have created yet another crypto mailing list to have the others on
board for GPZ4 because they are not allowed to hear about the L1 still
embargoed (Intel only) crap.

I pondered it for a bit, but then decided not to as its already bad enough
to have one crypto list to deal with. And dealing with the extra nonsense
of figuring out which list is for what and then having parallel discussions
about the same thing on both lists is just not workable.

I gave them access to the sysfs/prctl/seccomp and command line bits though,
so they could align their work on ours. I offered them to merge their stuff
through the sekrit git repo, but they have their own plans it seems.

I told Intel that we want the others here and that we can stop talking
about the L1 fuckup until GPZ4 is public and Intel agreed. That was at
least 4 weeks ago.

But the only two people who were allowed on the list are Tom Lendacky and
Alexei Starovoitov. The ARM/PowerPC people were still under discussion
@Intel end of last week. Useful...

Getting Tom in took only 3 weeks. For Greg it was 6 weeks and I had to push
hard to get it done. Alexei was pushed through by Dave Hansen, no idea how
long it took him to get there.

So in general the situation was more workable than last time, but far from
being great.

The right thing for stuff like this is treating us as adult and responsible
people and let us work it out on our own without being babysitted by Intel
and their disfunctional and agonizingly slow bureaucraZy. 

Seriously, the whole foofaraw about the L1 fuckup is just an idiotic
secrecy spectacle.

Thanks,

	tglx




  reply	other threads:[~2018-05-21 15:23 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       ` Thomas Gleixner [this message]
2018-05-21 16:46   ` 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         ` [MODERATED] Date/Time? Jon Masters
2018-05-21 20:43           ` 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=alpine.DEB.2.21.1805211647240.1599@nanos.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --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.