public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhltc@us.ibm.com>
To: "lkml, " <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	"Stultz, John" <johnstul@us.ibm.com>
Subject: kthrt vs rt13
Date: Tue, 22 Nov 2005 15:26:46 -0800	[thread overview]
Message-ID: <4383A936.8020507@us.ibm.com> (raw)

I am trying to determine which ktimers / hrt related patches are part of the rt 
series of patches and having some diffculty doing so.  I've heard it said that 
the wish is for people to evaluate the rt series as a standalone patch, rather 
than a collection of others.  I can understand this point of view, but in the 
case where someone is migrating from a kthrt kernel to an rt kernel and wants to 
verify that certain bugfixes etc have been applied, it would be very nice to be 
able to see the patch series file.  Can anyone provide such a list?

Thanks,

-- 
Darren Hart
IBM Linux Technology Center
Linux Kernel Team


             reply	other threads:[~2005-11-22 23:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 23:26 Darren Hart [this message]
2005-11-23  8:42 ` kthrt vs rt13 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=4383A936.8020507@us.ibm.com \
    --to=dvhltc@us.ibm.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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