From: Jan Kiszka <jan.kiszka@siemens.com>
To: Greg Gallagher <greg@embeddedgreg.com>,
Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: xenomai@lists.linux.dev
Subject: Re: arm/arm-64 ipipe release
Date: Mon, 20 Feb 2023 07:42:35 +0100 [thread overview]
Message-ID: <9a49e98f-2de6-168d-51b2-22c68c2d8084@siemens.com> (raw)
In-Reply-To: <CALLqZ8Sk2OejX_aZRSiMqdDunY-5nG_Gr5Guf032HhS41ewD=Q@mail.gmail.com>
On 20.02.23 06:27, Greg Gallagher wrote:
> On Sat, Feb 18, 2023 at 12:33 AM Greg Gallagher <greg@embeddedgreg.com> wrote:
>>
>> On Tue, Feb 14, 2023 at 11:56 AM Florian Bezdeka
>> <florian.bezdeka@siemens.com> wrote:
>>>
>>> Hi Greg!
>>>
>>> On Mon, 2023-02-13 at 23:01 -0500, Greg Gallagher wrote:
>>>> Hi,
>>>> I'm almost ready to release the next arm and arm64 ipipe patch. I'm
>>>> working on stable release 231 since it contains the patch that
>>>> hopefully fixes the UART irq issue seen in CI. If there's a problem
>>>> with using 231 let me know. Finishing my local test this week.
>>>
>>> Thanks for letting us know. If there is a chance that you publish a
>>> public available -rc somewhere, it would be possible to tweak our CI a
>>> bit and trigger a full test run in our lab.
>>>
>>> That should help us to identify any leftovers upfront.
>>>
>>> Best regards,
>>> Florian
>>>
>>>
>>>>
>>>> Thanks
>>>>
>>>> Greg
>>>>
>>>
>>
>> I'll get -rc releases out this weekend. I'll post back once they are
>> done and the -rc tags are pushed up.
>>
>> Thanks
>>
>> Greg
>
> Hi Florian,
> I have the rc releases ready to go. I'm going to push them up to
> the ipipe tree with the kernel update (5.4.231). Does the CI system
> pull the current ipipe release based on the tag? Would pushing up the
> new point release (5.4.231) break the current CI?
We are pulling from the head of ipipe/4.19.y-cip and ipipe/5.4.y for
ipipe-arm[64], see [1]. It just takes manual triggers so far as there
are no ci files in our kernel trees (unlike the xenomai repo itself).
Jan
[1]
https://source.denx.de/Xenomai/xenomai-images/-/blob/master/recipes-kernel/linux/linux-xenomai_latest.bb
--
Siemens AG, Technology
Competence Center Embedded Linux
next prev parent reply other threads:[~2023-02-20 6:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 4:01 arm/arm-64 ipipe release Greg Gallagher
2023-02-14 16:56 ` Florian Bezdeka
2023-02-18 5:33 ` Greg Gallagher
2023-02-20 5:27 ` Greg Gallagher
2023-02-20 6:42 ` Jan Kiszka [this message]
2023-02-28 5:18 ` Greg Gallagher
2023-02-28 5:48 ` Jan Kiszka
2023-02-28 7:49 ` Florian Bezdeka
2023-02-28 8:12 ` Jan Kiszka
2023-03-01 11:19 ` Florian Bezdeka
2023-03-01 12:08 ` Jan Kiszka
2023-03-03 17:50 ` Florian Bezdeka
2023-03-06 5:18 ` Greg Gallagher
2023-03-16 20:11 ` Greg Gallagher
2023-03-16 20:52 ` Florian Bezdeka
2023-03-16 20:56 ` Greg Gallagher
2023-03-16 23:42 ` Florian Bezdeka
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=9a49e98f-2de6-168d-51b2-22c68c2d8084@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=greg@embeddedgreg.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 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).