DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Xueming Li <xuemingl@nvidia.com>
Cc: stable@dpdk.org, dev@dpdk.org,
	Kevin Traynor <ktraynor@redhat.com>,
	 Luca Boccassi <bluca@debian.org>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: Re: 22.11.2 patches review and test
Date: Mon, 24 Apr 2023 08:53:30 +0200	[thread overview]
Message-ID: <CAJFAV8zRy-TCqr9f_g68=gOC=XX1DECFC2GovPtuyB4T8MUFBQ@mail.gmail.com> (raw)
In-Reply-To: <20230423093414.7546-1-xuemingl@nvidia.com>

Hello Xueming,

On Sun, Apr 23, 2023 at 11:35 AM Xueming Li <xuemingl@nvidia.com> wrote:
>
> Here is a list of patches targeted for stable release 22.11.2.
>
> The planned date for the final release is 5th MAY.
>
> Please help with testing and validation of your use cases and report
> any issues/results with reply-all to this mail. For the final release
> the fixes and reported validations will be added to the release notes.
>
> A release candidate tarball can be found at:
>
>     https://dpdk.org/browse/dpdk-stable/tag/?id=v22.11.2-rc1
>
> These patches are located at branch 22.11 of dpdk-stable repo:
>     https://dpdk.org/browse/dpdk-stable/
>
> Thanks.

Looking at the UNH dashboard, I see a build failure for Alpine on the
22.11 branch.
You probably need bc1db4f45af3 ("build: detect backtrace availability").


-- 
David Marchand


  reply	other threads:[~2023-04-24  6:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23  9:34 Xueming Li
2023-04-24  6:53 ` David Marchand [this message]
2023-04-25  6:06   ` Xueming(Steven) Li
2023-04-27  8:10 ` Xu, HailinX
2023-05-05  6:39   ` Xu, HailinX
2023-04-30 17:00 ` Ali Alnubani

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='CAJFAV8zRy-TCqr9f_g68=gOC=XX1DECFC2GovPtuyB4T8MUFBQ@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=ktraynor@redhat.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --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).