linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Venkat Subbiah <venkat.subbiah@cavium.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: rt patch set and tags on mainline repo
Date: Wed, 5 Oct 2011 21:47:28 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.02.1110052143420.18778@ionos> (raw)
In-Reply-To: <4E8CA60F.3080700@cavium.com>

On Wed, 5 Oct 2011, Venkat Subbiah wrote:

> Hello,
> 
> I am still not able to figure out which of Linus's tag in the mainline repo
> would an rt patch set apply to.
> 
> For example this patch here
> http://web.archive.org/web/20110612145812/http://www.kernel.org/pub/linux/kernel/projects/rt/patch-2.6.33.9-rt31.gz 

2.6.33.9-rt applies to 2.6.33.9 which is a stable release. Stable
kernels are not part of Linus tree. 

http://git.kernel.org/?p=linux/kernel/git/stable/linux-stable.git;a=shortlog;h=refs/heads/linux-2.6.33.y

> Q1) Alsolooks like the https://rt.wiki.kernel.org/index.php/Main_Page is still
> not available. Is there a location where I can get the split patch equivalent
> of "patch-2.6.33.9-rt31.gz".

Not at the moment.
 
> Q2) I am really looking to patch a 2.6.32 kernel. Are there rt patch sets
> available for this version even if they are unofficial?

No. Just my 0,01$: Move your BSP to 2.6.33 or 3.0 instead of
attempting to backport rt to 33. But it's your decision and your time
to waste. :0

Thanks,

	tglx

  reply	other threads:[~2011-10-05 19:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05 18:46 rt patch set and tags on mainline repo Venkat Subbiah
2011-10-05 19:47 ` Thomas Gleixner [this message]
2011-10-06  3:41   ` Venkat Subbiah
2011-10-06  7:13     ` 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=alpine.LFD.2.02.1110052143420.18778@ionos \
    --to=tglx@linutronix.de \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=venkat.subbiah@cavium.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).