linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Thomas Gleixner <tglx@linutronix.de>,
	<linux-rt-users@vger.kernel.org>
Subject: Re: [3.4-rt] backport of completion-use-simple-wait-queues.patch
Date: Fri, 29 Nov 2013 18:29:47 -0500	[thread overview]
Message-ID: <20131129232946.GA31239@windriver.com> (raw)
In-Reply-To: <20131129172155.64ac1eef@gandalf.local.home>

[Re: [3.4-rt] backport of completion-use-simple-wait-queues.patch] On 29/11/2013 (Fri 17:21) Steven Rostedt wrote:

> Burp!  /me is still recovering from Turkey day.

I'm jealous.  :)   [and now craving turkey...]

> 
> On Fri, 29 Nov 2013 10:11:13 -0500
> Paul Gortmaker <paul.gortmaker@windriver.com> wrote:
> 
> > 
> > Thanks for spotting that.  I guess the completion patch wouldn't hurt
> > to be in 3.4-rt anyway, but it is more a feature than a fix, it now seems.
> > [Not sure if Steve is still adding to the v3.4-rt-features branch...]
> 
> If people actually showed real interest for that branch, I would. But I
> haven't heard anything about anyone using it, so I haven't wasted my
> time on it.

So while we've not used it directly, we have definitely used the content
on that branch (i.e. rebasing to latest stable and logistical details
like that that would preclude direct use).  And while having it on
3.4-rt-features wasn't critically important, in that the content was
obviously present on newer releases, it did add a certain value in the
fact that folks in the know were indicating that the backports made
sense, and it wasn't just me alone wondering if the backport was valid.

With all the RT releases, and doing some stable baseline releases to
support them that you do, I'd not want to say that 3.4-rt-features
should get any special attention.  But at the same time, I'd not want
you to think it was a complete waste of time either.  I expect it is the
same for others, but in the typical haste of getting things done, and
the general level of "silent" users that was discussed at RTLWS, I do
suspect that once again, unfortunately nobody has bothered to
actually explicitly say "hey, thanks - we are glad this exists".

So, I'll start  -- thanks Steve. :)

Too little, too late?  Perhaps.  But better late than never, I hope.
`
Paul.

      reply	other threads:[~2013-11-29 23:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-28 20:10 [3.4-rt] backport of completion-use-simple-wait-queues.patch Paul Gortmaker
2013-11-29 12:49 ` Sebastian Andrzej Siewior
2013-11-29 15:11   ` Paul Gortmaker
2013-11-29 22:21     ` Steven Rostedt
2013-11-29 23:29       ` Paul Gortmaker [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=20131129232946.GA31239@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=bigeasy@linutronix.de \
    --cc=linux-rt-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).