From: Luca Boccassi <bluca@debian.org>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: Patrick Robb <probb@iol.unh.edu>, ci@dpdk.org, dev <dev@dpdk.org>,
Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
stable@dpdk.org, "Xueming(Steven) Li" <xuemingl@nvidia.com>
Subject: Re: meson error on ARM Grace server 23.11/22.11
Date: Tue, 29 Apr 2025 12:03:46 +0100 [thread overview]
Message-ID: <CAMw=ZnTJbf_-V4UP-=xDmgOXYvhTxgs87yimSo==+jK=nPn40g@mail.gmail.com> (raw)
In-Reply-To: <8fd14d21-dea3-48ea-afd3-ae347f566bb1@redhat.com>
On Tue, 29 Apr 2025 at 09:31, Kevin Traynor <ktraynor@redhat.com> wrote:
>
> +cc Luca/Xueming
>
> On 29/04/2025 03:43, Patrick Robb wrote:
> > Hi,
> >
> > At the DPDK Community Lab we have been running CI tests with a new ARM
> > Grace server for the past couple of months on main and next-* branches. I
> > am trying to add LTS runs now, and ran into a snag with 23.11 and 22.11 for
> > this system. Stable maintainers I'm not sure whether this should be
> > addressed or not for hardware which is new and didn't exist when 22.11 and
> > 23.11 were released... but I figured I'd make the tickets and find out. I
> > attached the meson logs to the tickets and if for whatever reason you guys
> > want to remote into this machine, I'm happy to setup the VPN and SSH
> > access.
> >
> > 22.11: https://bugs.dpdk.org/show_bug.cgi?id=1703
> > 23.11: https://bugs.dpdk.org/show_bug.cgi?id=1702
Assuming this only requires some changes in meson to accommodate, I'd
be fine in accepting a patch for 22.11 that enables it, if someone
were to send it. If it requires more invasive changes then it would
need to be evaluated for risk.
next prev parent reply other threads:[~2025-04-29 11:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-29 2:43 Patrick Robb
2025-04-29 8:30 ` Kevin Traynor
2025-04-29 11:03 ` Luca Boccassi [this message]
2025-04-29 15:59 ` Wathsala Wathawana Vithanage
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='CAMw=ZnTJbf_-V4UP-=xDmgOXYvhTxgs87yimSo==+jK=nPn40g@mail.gmail.com' \
--to=bluca@debian.org \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=honnappa.nagarahalli@arm.com \
--cc=ktraynor@redhat.com \
--cc=probb@iol.unh.edu \
--cc=stable@dpdk.org \
--cc=xuemingl@nvidia.com \
/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).