From mboxrd@z Thu Jan  1 00:00:00 1970
Return-path: <SRS0=nia/=II=linuxfoundation.org=gregkh@kernel.org>
Received: from mail.kernel.org ([198.145.29.99])
	by Galois.linutronix.de with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
	(Exim 4.80)
	(envelope-from <SRS0=nia/=II=linuxfoundation.org=gregkh@kernel.org>)
	id 1fKe7Q-0004J2-Ca
	for speck@linutronix.de; Mon, 21 May 2018 08:16:28 +0200
Date: Mon, 21 May 2018 08:16:03 +0200
From: Greg KH <gregkh@linuxfoundation.org>
Subject: [MODERATED] Re: Date/Time?
Message-ID: <20180521061603.GC5529@kroah.com>
References: <20180519172627.GB1239@kroah.com>
 <ab610f46-9e42-a9f6-5a79-65be1f3dc552@redhat.com>
MIME-Version: 1.0
In-Reply-To: <ab610f46-9e42-a9f6-5a79-65be1f3dc552@redhat.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: speck@linutronix.de
List-ID: <speck.linutronix.de>

On Sun, May 20, 2018 at 04:59:04PM -0400, speck for Jon Masters wrote:
> On 05/19/2018 01:26 PM, speck for Greg KH wrote:
> 
> > Jon, I know you were talking to people working on other arches, any
> > ideas when I should be expecting to see patches I can backport to get
> > into devices/distros?
> 
> Sorry for lag. In flight back from a funeral. Here's the latest below.
> Then please see my rant (not directed at anyone here) at the end that
> makes me think I should maintain a tree next time to get these to you.

<snip of the summary>

Thanks for this, much appreciated.

Sad to see there is no other arch that is going to be ready, wonderful :(

> And now my little rant. It is clear (to me) that Intel know how to
> handle some of this better than others. The next time there is an issue,
> I am going to cajole all of the vendors as usual, but I will also make
> sure Greg, Linus, and Thomas are read in early enough that we can go
> figure out the best way to handle the other arches. If that's me hosting
> a git tree, great. Whatever you need. But we need to fix this next time.

As Linus said, hah!  Intel only "handled this better" because of Thomas
pushing them (the effort it took to get me here was crazy...)

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.

Oh well, baby steps, maybe next time will be better, but I'm not holding
my breath.

greg k-h