From: Russell Johnson <russell.johnson@kratosdefense.com>
To: Philippe Gerum <rpm@xenomai.org>
Cc: "xenomai@lists.linux.dev" <xenomai@lists.linux.dev>,
Bryan Butler <Bryan.Butler@kratosdefense.com>,
Shawn McManus <shawn.mcmanus@kratosdefense.com>
Subject: RE: [External] - Re: EVL Memory
Date: Thu, 17 Nov 2022 22:19:10 +0000 [thread overview]
Message-ID: <PH1P110MB105036766C938742737AC56EE2069@PH1P110MB1050.NAMP110.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87pmdlbjg7.fsf@xenomai.org>
[-- Attachment #1: Type: text/plain, Size: 314 bytes --]
So I can build v5.15.y-evl-rebase just fine on multiple systems (using plain
make and using make rpm-pkg). I cannot build the latest next-evl-rebase
branch on any of my systems (using plain make and using make rpm-pkg). There
must have been something that changed in recent commits.. Any ideas?
Thanks,
Russell
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 6759 bytes --]
next prev parent reply other threads:[~2022-11-17 22:19 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <PH1P110MB1050AD875FCD924D827A0A54E23E9@PH1P110MB1050.NAMP110.PROD.OUTLOOK.COM>
[not found] ` <PH1P110MB10508DD9688B7D0E82AB30CDE23E9@PH1P110MB1050.NAMP110.PROD.OUTLOOK.COM>
2022-11-09 17:04 ` EVL Memory Russell Johnson
2022-11-09 17:20 ` Philippe Gerum
2022-11-11 21:34 ` [External] - " Russell Johnson
2022-11-14 9:53 ` Philippe Gerum
2022-11-14 22:42 ` Russell Johnson
2022-11-15 8:33 ` Philippe Gerum
2022-11-15 17:05 ` Russell Johnson
2022-11-15 18:36 ` Philippe Gerum
2022-11-16 15:48 ` Philippe Gerum
2022-11-16 21:37 ` Russell Johnson
2022-11-17 16:48 ` Philippe Gerum
2022-11-17 16:57 ` Russell Johnson
2022-11-17 17:03 ` Philippe Gerum
2022-11-17 17:37 ` Russell Johnson
2022-11-18 8:06 ` Philippe Gerum
2022-11-18 21:08 ` Russell Johnson
2022-11-17 22:19 ` Russell Johnson [this message]
2022-11-18 8:02 ` Philippe Gerum
2022-11-18 8:08 ` Philippe Gerum
2022-11-19 16:37 ` Russell Johnson
2022-11-19 16:42 ` Philippe Gerum
2022-11-19 16:50 ` Russell Johnson
2022-11-19 18:11 ` Russell Johnson
2022-11-20 8:25 ` Philippe Gerum
2022-11-21 15:56 ` Philippe Gerum
2022-11-21 18:33 ` Bryan Butler
2022-11-28 15:21 ` Russell Johnson
2022-11-28 16:49 ` Philippe Gerum
2022-11-28 20:59 ` Russell Johnson
[not found] ` <0082bff2d91b0125ac60050159d3003e64b45bffa35e0c4f0ed9799e38b97b8c@mu>
2022-11-30 15:57 ` Philippe Gerum
2022-12-01 14:36 ` Philippe Gerum
2022-12-01 20:01 ` Russell Johnson
2022-12-02 9:18 ` Philippe Gerum
2022-12-02 15:12 ` Russell Johnson
2022-12-02 15:27 ` Philippe Gerum
2022-12-02 15:38 ` Philippe Gerum
2022-12-02 20:50 ` Russell Johnson
2022-12-03 11:37 ` Philippe Gerum
2022-12-02 15:48 ` Russell Johnson
2022-12-02 16:50 ` Philippe Gerum
2022-12-02 17:22 ` Philippe Gerum
2022-12-02 22:26 ` Russell Johnson
2022-12-03 11:37 ` Philippe Gerum
2022-12-03 15:44 ` Philippe Gerum
2022-12-04 11:05 ` Philippe Gerum
2022-12-04 18:05 ` Philippe Gerum
2022-12-04 18:43 ` Russell Johnson
2022-12-05 6:53 ` Russell Johnson
2022-12-05 6:59 ` Russell Johnson
2022-12-05 8:24 ` Philippe Gerum
2022-12-05 16:31 ` Russell Johnson
2022-12-05 16:38 ` Russell Johnson
2022-12-05 17:01 ` Philippe Gerum
2022-12-05 8:45 ` Philippe Gerum
2022-11-14 23:33 ` Russell Johnson
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=PH1P110MB105036766C938742737AC56EE2069@PH1P110MB1050.NAMP110.PROD.OUTLOOK.COM \
--to=russell.johnson@kratosdefense.com \
--cc=Bryan.Butler@kratosdefense.com \
--cc=rpm@xenomai.org \
--cc=shawn.mcmanus@kratosdefense.com \
--cc=xenomai@lists.linux.dev \
/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.