historical-speck.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: Re: LVI
Date: Thu, 21 Nov 2019 01:50:05 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.21.1911210129090.29534@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20191120191942.GA3086925@kroah.com>

On Wed, 20 Nov 2019, speck for Greg KH wrote:
> On Wed, Nov 20, 2019 at 08:09:43PM +0100, speck for Peter Zijlstra wrote:
> > On Wed, Nov 20, 2019 at 06:25:29PM +0100, speck for Greg KH wrote:
> > > > > 
> > > > > 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?  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?
> > 
> > Please, no keybase, kill and exterminate that crap.
> 
> For sending pictures of people drinking beer, it's fine.  For trying to
> talk about technical things, it's horrid.
> 
> But, there is a git plugin and there is a repo that uses it, see the
> other email for details on how to clone it.  I can live with that for
> basic things like "list of issues / disclosure dates" as long as people
> keep it up to date.

This requires to have a keybase account in the first place. Which I don't
have and Peter neither. I don't have one because back then when this
keybase thingy started participation was requiring some form of social
media ID (what a retarded security concept) which I don't have.

Just for the record. We are fixing Intel's crap and it's Intel's
repsonsibility to make information accessible to us in ways which do not
force us to use randomly chosen chit-chat infrastructure which happens to
have a git repository associated. Do I have to repeat that forever?

If there is a way to submit a ssh key to get access to that git repository
without telling the farcebooks and gurgles of this world about me, then I
might be in.

Alternatively I'm happy to give write access to a speck repo branch or a
seperate repo, which is accessible to this group by old fashioned, but
halfways trustable technology, to someone who volunteers to sync that
stuff.

Thanks,

	tglx

  reply	other threads:[~2019-11-21  0:50 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
2019-11-20 19:09     ` Peter Zijlstra
2019-11-20 19:19       ` Greg KH
2019-11-21  0:50         ` Thomas Gleixner [this message]
2019-11-21 13:45           ` 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=alpine.DEB.2.21.1911210129090.29534@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 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).