All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: speck@linutronix.de
Subject: [MODERATED] Re: Date/Time?
Date: Mon, 21 May 2018 08:16:03 +0200	[thread overview]
Message-ID: <20180521061603.GC5529@kroah.com> (raw)
In-Reply-To: <ab610f46-9e42-a9f6-5a79-65be1f3dc552@redhat.com>

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

  parent reply	other threads:[~2018-05-21  6:16 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 [this message]
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         ` [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=20180521061603.GC5529@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --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.