From: ben.hutchings@codethink.co.uk (Ben Hutchings)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] [OBSOLETE?] CONFIG_PREEMPT_RT_FULL config parameter in 4.19?!
Date: Fri, 19 Jul 2019 19:11:24 +0100 [thread overview]
Message-ID: <5c024c43245bd5cdecd256fe9d74d6992ea95598.camel@codethink.co.uk> (raw)
In-Reply-To: <CAEss1E+93RuXzGWeNMaTreUaMOObmNioB5=VGD0qjgerYTFf6Q@mail.gmail.com>
On Fri, 2019-07-19 at 19:58 +0200, Zoran S wrote:
> > This never existed in the upstream kernel, only in -rt branches.
> > It still exists in 4.19-rt.
>
> Sure. The following is done by me:
>
> git clone git://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git
>
> Isn't this CIP RT-kernel real-time tree?
[...]
It's the CIP kernel repository. Only the branches with "-rt" in the
name include the real-time patch set.
Ben.
--
Ben Hutchings, Software Developer Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom
next prev parent reply other threads:[~2019-07-19 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-19 13:31 [cip-dev] [OBSOLETE?] CONFIG_PREEMPT_RT_FULL config parameter in 4.19?! Zoran S
2019-07-19 13:58 ` Ben Hutchings
2019-07-19 17:58 ` Zoran S
2019-07-19 18:11 ` Ben Hutchings [this message]
2019-07-19 19:03 ` Zoran S
2019-07-19 19:08 ` Daniel Wagner
2019-07-19 13:59 ` Pavel Machek
2019-07-19 18:05 ` Zoran S
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=5c024c43245bd5cdecd256fe9d74d6992ea95598.camel@codethink.co.uk \
--to=ben.hutchings@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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