From: Radu Rendec <radu.rendec@gmail.com>
To: jan.kiszka@siemens.com
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] ipipe-4.4.y LTS
Date: Tue, 19 Jun 2018 09:55:34 -0400 [thread overview]
Message-ID: <CAD5jUk-CijJ=LhouoHwwS2ZX=gmqjR7a_fWczYWFu9ze6PLqrQ@mail.gmail.com> (raw)
In-Reply-To: <3286435f-71ae-874d-72a5-5a7cbef0d550@siemens.com>
On Tue, Jun 19, 2018 at 3:09 AM Jan Kiszka <jan.kiszka@siemens.com> wrote:
>
> On 2018-06-18 15:59, Greg Gallagher wrote:
> > Are there still plans to have a ipipe patch for the CIP kernel? I
> > think this was brought up at the last meet up? Maybe the bigger
> > question (which is a lot more work) is do we plan on maintaining ipipe
> > for 4.4, 4.9 and older?
>
> Yes, there are plans to go over 4.4-CIP. So far, I'm only maintaining
> based on 4.4-LTS, just tested on x86, pushed to
> https://lab.xenomai.org/ipipe-jki.git/log/?h=for-upstream/4.4-update.
> Would be happy to receive contributions in form of tests on other
> architectures!
That's great news! Thanks for the hard work! I'm targeting powerpc, so I
will probably get back with some test results during the next couple of
weeks.
Looking at the history in Jan's tree, it seems "for-upstream/4.4-update"
is updated quite often. Perhaps it would be a good idea to keep the
ipipe-4.4.y branch in sync or at least advertise Jan's tree on the
Xenomai website. It would be useful for people like me who are interested
in a recent 4.4-LTS version of ipipe.
Thanks,
Radu
next prev parent reply other threads:[~2018-06-19 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 12:52 [Xenomai] ipipe-4.4.y LTS Radu Rendec
2018-06-18 13:59 ` Greg Gallagher
2018-06-19 7:09 ` Jan Kiszka
2018-06-19 13:55 ` Radu Rendec [this message]
2018-06-19 14:03 ` Philippe Gerum
2018-06-19 14:09 ` Greg Gallagher
2018-06-19 14:36 ` Philippe Gerum
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='CAD5jUk-CijJ=LhouoHwwS2ZX=gmqjR7a_fWczYWFu9ze6PLqrQ@mail.gmail.com' \
--to=radu.rendec@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=xenomai@xenomai.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.