From: Ralf Mardorf <ralf.mardorf@alice-dsl.net>
To: linux-rt-users@vger.kernel.org
Subject: Re: RT patchset naming convention
Date: Sat, 30 Dec 2017 06:27:18 +0100 [thread overview]
Message-ID: <20171230062718.1454b6e8@archlinux.localdomain> (raw)
In-Reply-To: <CAF_dkJDQy-ONu59RG4HbiuYPEm+DA1zqME8pQp7VdUspcsptVA@mail.gmail.com>
This one didn't came through:
Date: Sat, 30 Dec 2017 06:07:28 +0100
From: Ralf
To: linux-rt-users
Subject: Re: RT patchset naming convention
On Fri, 29 Dec 2017 19:34:43 -0500, Patrick Doyle wrote:
>Is there documentation as to the naming convention?
>patches-4.9.61-rt61.tar.gz
^^^^^^ ^^^^rt patch version
^^^^^^kernel version
https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.9.tar.gz
+
https://www.kernel.org/pub/linux/kernel/v4.x/patch-4.9.61.gz
or
https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.9.61.tar.gz
Rt patches that fit to kernel 4.9.61 are all patches
4.9.61-rt*
See also https://cdn.kernel.org/category/releases.html .
>Sadly, I don't see any patches for any 4.9.5? releases. So is there
>any advice as to which patch set I should apply to my kernel?
Is there a good reason that has to be exactly 4.9.5?
Why don't you follow the 4.9 LTS as close a s possible by upgrading to
a kernel version close to an available rt patch.
4.9.73 is from 2017-12-29, see https://cdn.kernel.org/ ,
IOW I would go with kernel 4.9.68 and patch-4.9.68-rt60
If you really want 4.9.5 you could try to do it as Fernando from CCRMA
does:
https://lists.linuxaudio.org/pipermail/linux-audio-user/2017-December/109022.html
That way a patch might apply automatically with an offset or you
perhaps need to fix it manually.
prev parent reply other threads:[~2017-12-30 5:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-30 0:34 RT patchset naming convention Patrick Doyle
2017-12-30 5:07 ` Ralf Mardorf
2017-12-30 5:18 ` Ralf Mardorf
2017-12-30 5:20 ` Ralf Mardorf
2017-12-30 11:21 ` Arve Barsnes
2017-12-30 14:37 ` Patrick Doyle
2017-12-30 5:27 ` Ralf Mardorf [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=20171230062718.1454b6e8@archlinux.localdomain \
--to=ralf.mardorf@alice-dsl.net \
--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).