All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: rt-users <linux-rt-users@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Clark Williams <williams@redhat.com>,
	nando@ccrma.Stanford.EDU, Carsten Emde <ce@ceag.ch>
Subject: [ANNOUNCE] 2.6.33-rt3
Date: Fri, 26 Feb 2010 20:54:25 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1002262041020.4245@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.1002241740410.4245@localhost.localdomain>

We are pleased to announce the next update to our new preempt-rt
series.

    - Update to 2.6.33

    - rt fixes:

      	 Peter Zijlstra (1):
    	       highmem, -rt: Implement pfn and prot kmaps

	Thomas Gleixner (2):
      	       x86: pci: Prevent mmconfig memory corruption
      	       mmc: omap_hsmmc: Fix the locking mess

A note on the development process:

  The rt/2.6.33 branch is now stabilization only. The rt/head branch
  will follow linus tree from now on, so it will inherit all
  (mis)features which come in the merge window.

Download locations:
   
   http://www.kernel.org/pub/linux/kernel/projects/rt/

Git development branch:
   git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/head

Git release branch:
   git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip.git rt/2.6.33

Gitweb:
   http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=shortlog;h=rt/2.6.33

Information on the RT patch can be found at:

   http://rt.wiki.kernel.org/index.php/Main_Page
 
To build the 2.6.33-rt3 tree, the following patches should be
applied:

   http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.33.tar.bz2
   http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33-rt3.bz2

Enjoy !

      tglx

  parent reply	other threads:[~2010-02-26 19:55 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24 16:52 [ANNOUNCE] 2.6.33-rc8-rt2 Thomas Gleixner
2010-02-24 22:38 ` Peter Zijlstra
2010-02-25 22:56   ` Peter Zijlstra
2010-02-26 19:44 ` Dan Carpenter
2010-02-27  8:10   ` Thomas Gleixner
2010-02-26 19:54 ` Thomas Gleixner [this message]
2010-02-27  9:25   ` [ANNOUNCE] 2.6.33-rt3 Xavier Miller
2010-02-27  9:25     ` Xavier Miller
2010-02-27 10:10     ` GeunSik Lim
2010-02-27 11:53     ` Thomas Gleixner
2010-03-02 21:25       ` Fernando Lopez-Lezcano
2010-03-02 21:53         ` Thomas Gleixner
2010-02-27  9:50   ` GeunSik Lim
2010-02-27  9:50     ` GeunSik Lim
2010-03-12 10:44   ` [ANNOUNCE] 2.6.33-rt6 Thomas Gleixner
2010-03-12 12:17     ` 2.6.33-rt6 on Beagle Chatterjee, Amit
2010-03-15  9:20       ` Uwe Kleine-König
2010-03-15 11:23         ` What's the best way to create an embedded version of PREEMPT_RT Linux ? Armin Steinhoff
2010-03-21 11:06     ` [ANNOUNCE] 2.6.33.1-rt11 Thomas Gleixner
2010-04-07 14:24       ` [ANNOUNCE] 2.6.33.2-rt13 Thomas Gleixner
2010-04-27 15:52         ` [ANNOUNCE] 2.6.33.3-rt16 Thomas Gleixner
2010-04-30 10:00           ` [ANNOUNCE] 2.6.33.3-rt17 Thomas Gleixner
2010-05-02 19:18             ` [ANNOUNCE] 2.6.33.3-rt19 Thomas Gleixner
2010-06-09 16:44               ` [ANNOUNCE] 2.6.33.5-rt23 Thomas Gleixner
2010-06-09 21:31                 ` Will Schmidt
2010-06-10  6:07                   ` Thomas Gleixner
2010-06-10 15:56                     ` Will Schmidt
2010-06-10 16:05                       ` Darcy L. Watkins
2010-06-14 13:33                         ` Thomas Gleixner
2010-06-14 13:34                       ` Thomas Gleixner
2010-06-14 15:35                         ` Will Schmidt
2010-07-13 15:54                 ` [ANNOUNCE] 2.6.33.6-rt26 Thomas Gleixner
2010-07-13 16:52                   ` Dhaval Giani
2010-07-13 18:04                   ` Philipp Überbacher
2010-07-13 19:13                     ` Darcy L. Watkins
2010-07-13 19:23                       ` Philipp Überbacher
2010-07-14 13:47                         ` Thomas Gleixner
2010-07-14 13:57                           ` Ng Oon-Ee
2010-07-14 14:27                             ` John Kacur
     [not found]                               ` <AANLkTikRUp0IG8aMZ0eHxXcDmfUFTqW8HCSJcx8nQIZN@mail.gmail.com>
2010-07-15  5:25                                 ` Yang Jian
2010-07-15 11:45                           ` Philipp Überbacher
2010-07-19  6:37                   ` Barry Song
2010-07-19  6:37                     ` Barry Song
2010-07-31 13:33                   ` [ANNOUNCE] 2.6.33.6-rt27 Thomas Gleixner
2010-08-03  9:23                     ` [ANNOUNCE] 2.6.33.7-rt29 Thomas Gleixner
2010-12-21 13:52                       ` Thomas Gleixner
2010-12-21 15:01                         ` Mark Knecht
2010-12-21 15:48                         ` Madovsky
2010-12-21 16:39                         ` Dennis Borgmann
2010-12-22 16:38                         ` Madovsky
2010-12-22 20:20                         ` Remy Bohmer
2010-12-24 22:36                         ` Fernando Lopez-Lezcano
2010-12-31 19:56                           ` Fernando Lopez-Lezcano
2010-12-31 19:56                             ` Fernando Lopez-Lezcano

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=alpine.LFD.2.00.1002262041020.4245@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=ce@ceag.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=williams@redhat.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 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.