linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henrik Austad <henrik@austad.us>
To: Ruud Commandeur <RCommandeur@clb.nl>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Applying rt-patches
Date: Thu, 19 Dec 2013 10:05:38 +0100	[thread overview]
Message-ID: <20131219090538.GA7167@austad.us> (raw)
In-Reply-To: <15AE5A936F5E3A42A9144E66875A0A8938ADEC@server1-derijp.CLB-Benelux.lokaal>

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

On Thu, Dec 19, 2013 at 09:35:33AM +0100, Ruud Commandeur wrote:
> Hi Everyone,

Hi Ruud,

> I'm using the Linux 3.10.x kernel for a while in an ARM9 embedded
> system. I keep this kernel up-to-date by using incremental patches, with
> 3.10.24 being the last version. I'm thinking of switching to the
> RT-kernel for better real-time behavior, but I have a few questions how
> to do that:
>  
> On a clean 3.10.24 kernel, I assume I should use the
> "patch-3.10.24-rt22.patch" archive (or the "patches-3.10.24-rt22" for a
> collection of single patch files).

Yes, that is correct.

> But what if a 3.10.25 kernel is released? Should I first apply the
> incremental patch for the kernel and then the incremental patch for the
> rt-part? Or should the 3.10.24-rt patch be reverted before applying the
> kernel patch to prevent conflicts?

Hmm, _personally_ I just use git and check out a new stable-branch and then 
apply the corresponding -rtX patch on top of that. Iẗ́'s a pretty big 
hammer, but it removes a lot of potentional snags (me being butterfingered 
an' all :)

If you have a set of local commits you want to carry with you, using the 
broken out rt-patches and 'git quiltimport' lets you quickly get everything 
into a branch.  Then you can cherry-pick the changes you want to add on top 
of that.

At least, this is -my- approach to the matter.

I also know that ro(a)sted keeps a git-repo which he moves forward, so you 
could add your own, local changes to it and just track using 'git pull 
--rebase' or some variant thereof. YMMW and all.
 
> Sorry if the answer to my questions would be somewhere in the Wiki, I
> was not able to find it myself up till now.

I think this is pretty much down to what works best for you, applying the 
incremental patches should probably work too, but I've never tried that 
approach myself. I just use the increments to track changes from one -rtX 
to the next.


-- 
Henrik Austad

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2013-12-19  9:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-19  8:35 Applying rt-patches Ruud Commandeur
2013-12-19  9:05 ` Henrik Austad [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=20131219090538.GA7167@austad.us \
    --to=henrik@austad.us \
    --cc=RCommandeur@clb.nl \
    --cc=linux-rt-users@vger.kernel.org \
    /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).