From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: Aaron Conole <aconole@redhat.com>,
dev@dpdk.org, Michael Santana <maicolgabriel@hotmail.com>
Subject: Re: [PATCH] ci: switch to Fedora 37
Date: Tue, 25 Apr 2023 16:20:50 -0700 [thread overview]
Message-ID: <20230425162050.4b90def3@hermes.local> (raw)
In-Reply-To: <CAJFAV8yDJJVuPmdRQ8r-bZHYjFMrFP3W-K-bbuG5dye32TD6fA@mail.gmail.com>
On Tue, 25 Apr 2023 15:13:50 +0200
David Marchand <david.marchand@redhat.com> wrote:
> Hello Aaron,
>
> On Fri, Apr 21, 2023 at 11:06 PM Aaron Conole <aconole@redhat.com> wrote:
> > David Marchand <david.marchand@redhat.com> writes:
> > > Fedora 35 has been declared EOL in 2022/12 (see [1]).
> > > Fedora 36 will soon be EOL too.
> > >
> > > Move to Fedora 37.
> > > Fedora 37 libbpf does not support AF_XDP anymore, now provided by
> > > libxdp.
> > >
> > > 1: https://docs.fedoraproject.org/en-US/releases/eol/
> > >
> > > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > > ---
> >
> > Acked-by: Aaron Conole <aconole@redhat.com>
> >
> > FYI, Fedora 38 also just got released. Perhaps that can be a candidate
> > as well, but I didn't try it out.
>
> At a first glance, gcc 13 raises some new warnings, at least for
> examples (ip-pipeline and ntb).
> We can switch to f38 once builds are fine with gcc 13.
What errors, just tried and current main branch builds clean on new F38 VM.
next prev parent reply other threads:[~2023-04-25 23:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 14:34 David Marchand
2023-04-21 21:06 ` Aaron Conole
2023-04-25 13:13 ` David Marchand
2023-04-25 23:20 ` Stephen Hemminger [this message]
2023-04-26 5:45 ` David Marchand
2023-05-23 9:49 ` Thomas Monjalon
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=20230425162050.4b90def3@hermes.local \
--to=stephen@networkplumber.org \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.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).