From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: steven.monsees@baesystems.com
Cc: "yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Subject: Re: [yocto] yocto preempt-rt
Date: Tue, 2 Nov 2021 12:25:53 -0400 [thread overview]
Message-ID: <CADkTA4MK42-jw8yWWaHM8uDM=ayhJRqcdjEHq6zZDya+JswkQw@mail.gmail.com> (raw)
In-Reply-To: <MADEUP.16B3C74F343D36F7.18236@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 1135 bytes --]
Correct.
The rt patches are already integrated on the branches that that recipe will
build out of the linux-yocto repository.
Bruce
On Tue, Nov 2, 2021 at 12:23 PM Monsees, Steven C (US) via
lists.yoctoproject.org <steven.monsees=baesystems.com@lists.yoctoproject.org>
wrote:
>
>
> Is it true that no patch work is required if out under
>
> …/poky/meta/recipes-kernel, there exists a yocto-linux-rt_##.##.bb recipe
> that matches your kernel release?, and that it will build the full
> preemptive RT Kernel ?
>
>
>
> Thanks,
>
> Steve
>
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#55215):
> https://lists.yoctoproject.org/g/yocto/message/55215
> Mute This Topic: https://lists.yoctoproject.org/mt/86770123/1050810
> Group Owner: yocto+owner@lists.yoctoproject.org
> Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [
> bruce.ashfield@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
>
--
- Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end
- "Use the force Harry" - Gandalf, Star Trek II
[-- Attachment #2: Type: text/html, Size: 2657 bytes --]
next parent reply other threads:[~2021-11-02 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MADEUP.16B3C74F343D36F7.18236@lists.yoctoproject.org>
2021-11-02 16:25 ` Bruce Ashfield [this message]
2021-11-02 16:34 ` [yocto] yocto preempt-rt Leon Woestenberg
2021-11-02 16:53 ` Mittal, Anuj
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='CADkTA4MK42-jw8yWWaHM8uDM=ayhJRqcdjEHq6zZDya+JswkQw@mail.gmail.com' \
--to=bruce.ashfield@gmail.com \
--cc=steven.monsees@baesystems.com \
--cc=yocto@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.