linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bob Ham <rah@bash.sh>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Bryan Donlan <bdonlan@gmail.com>,
	Shawn Starr <shawn.starr@rogers.com>,
	linux-kernel@vger.kernel.org, RT <linux-rt-users@vger.kernel.org>
Subject: Re: State of Linux-RT Patches and full inclusion into linus tree
Date: Sun, 17 Jul 2011 14:58:42 +0100	[thread overview]
Message-ID: <1310911122.7557.2.camel@myrtle.6gnip.net> (raw)
In-Reply-To: <20110711065437.6c913cca@bike.lwn.net>

[-- Attachment #1: Type: text/plain, Size: 632 bytes --]

On Mon, 2011-07-11 at 06:54 -0600, Jonathan Corbet wrote:
> On Mon, 11 Jul 2011 00:46:31 -0400
> Bryan Donlan <bdonlan@gmail.com> wrote:
> 
> > On Sun, Jul 10, 2011 at 20:43, Shawn Starr <shawn.starr@rogers.com> wrote:

> > > I was wondering if (or ever) will the full Linux RT patches be merged into
> > > Linus's tree?

> Thomas gave a talk on this subject back in April:
> 
> 	http://lwn.net/Articles/440064/

That article contains the following sentence:

  "There are plans to update to 2.6.38 soon."

Just out of curiosity, is that update under way?

-- 
Bob Ham <rah@bash.sh>

for (;;) { ++pancakes; }

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2011-07-17 14:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1449505.pSCLrkaxpL@segfault.sh0n.net>
2011-07-11  4:46 ` State of Linux-RT Patches and full inclusion into linus tree Bryan Donlan
2011-07-11  5:43   ` jordan
2011-07-11 12:54   ` Jonathan Corbet
2011-07-17 13:58     ` Bob Ham [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=1310911122.7557.2.camel@myrtle.6gnip.net \
    --to=rah@bash.sh \
    --cc=bdonlan@gmail.com \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=shawn.starr@rogers.com \
    /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).