xenomai.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Greg Gallagher <greg@embeddedgreg.com>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: xenomai@lists.linux.dev, Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: arm/arm-64 ipipe release
Date: Mon, 20 Feb 2023 00:27:07 -0500	[thread overview]
Message-ID: <CALLqZ8Sk2OejX_aZRSiMqdDunY-5nG_Gr5Guf032HhS41ewD=Q@mail.gmail.com> (raw)
In-Reply-To: <CALLqZ8SiSB8e1VJcCv06H7Gc=zwiLf=6kBisB73yCT6VhRRRug@mail.gmail.com>

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?

thanks

Greg

  reply	other threads:[~2023-02-20  5:27 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 [this message]
2023-02-20  6:42       ` Jan Kiszka
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='CALLqZ8Sk2OejX_aZRSiMqdDunY-5nG_Gr5Guf032HhS41ewD=Q@mail.gmail.com' \
    --to=greg@embeddedgreg.com \
    --cc=florian.bezdeka@siemens.com \
    --cc=jan.kiszka@siemens.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).