public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Sebastian Sewior <bigeasy@linutronix.de>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Carsten Emde <cbe@osadl.org>
Subject: Re: [ANNOUNCE] 3.4.10-rt7
Date: Mon, 07 Jul 2014 16:54:49 +0200	[thread overview]
Message-ID: <1404744889.4709.83.camel@marge.simpson.net> (raw)
In-Reply-To: <alpine.DEB.2.10.1407071027170.22031@nanos>

On Mon, 2014-07-07 at 14:47 +0200, Thomas Gleixner wrote: 
> Dear RT Folks,
> 
> I'm pleased to announce the 3.14.10-rt7 release. 3.14.10-rt6 is a not
> announced update to 3.14.10 without any RT changes aside of resolving
> the patch conflicts.
> 
> Changes since 3.14.10-rt6:
> 
>    * Do not clear PF_NO_SETAFFINITY flag in select_fallback_rq() -
>      from Steven
> 
>    * Prevent workqueue deadlock/stall observed with XFS
> 
> 
> A few words on the status and the future of RT:
> -----------------------------------------------
> 
> The situation since last years RTLWS (https://lwn.net/Articles/572740/)
> has not improved at all, it's worse than before. 
> 
> While shortly after RTLWS quite some people promised to whip up proper
> funding, nothing has materialized and my personal situation is worse
> than before.

Sorry to hear that funding hasn't as yet happened.

> I'm really tired of all the politics involved, the blantant lies and
> the marketing bullshit which I have to bear. I learned a few month ago
> that a certain kernel vendor invented most of RT anyway and is the
> expert in this field, so the customers dont have to worry about my
> statements.

Wow, so someone thinks their customers either can't or won't read.  That
kind of marketing can backfire in a big way.

-Mike



      parent reply	other threads:[~2014-07-07 14:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-07 12:47 [ANNOUNCE] 3.4.10-rt7 Thomas Gleixner
     [not found] ` <db211a08-b8e8-42ca-9d93-5737b589c3df@email.android.com>
2014-07-07 13:01   ` Thomas Gleixner
2014-07-07 14:34 ` [ANNOUNCE] 3.14.10-rt7 Thomas Gleixner
2014-07-09 10:01   ` Pavel Vasilyev
2014-07-09 11:34     ` Henrik Austad
2014-07-09 12:04       ` Pavel Vasilyev
2014-07-07 14:54 ` Mike Galbraith [this message]

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=1404744889.4709.83.camel@marge.simpson.net \
    --to=umgwanakikbuti@gmail.com \
    --cc=bigeasy@linutronix.de \
    --cc=cbe@osadl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@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