DPDK patches and discussions
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Luca Boccassi <bluca@debian.org>
Cc: stable@dpdk.org, dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: 20.11.5 patches review and test
Date: Mon, 28 Mar 2022 14:55:00 +0200	[thread overview]
Message-ID: <CAATJJ0LyvfmWOB811Y3Kf6GGErAVoF3uAaX-qE0GYQS5JFM2cg@mail.gmail.com> (raw)
In-Reply-To: <0ec94c4d87d437bd8298927c40c14340d22b18e3.camel@debian.org>

[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]

On Mon, Mar 28, 2022 at 1:50 PM Luca Boccassi <bluca@debian.org> wrote:

> On Mon, 2022-03-28 at 09:40 +0200, Christian Ehrhardt wrote:
> > On Fri, Mar 18, 2022 at 4:21 PM <luca.boccassi@gmail.com> wrote:
> > >
> > > Hi all,
> > >
> > > Here is a list of patches targeted for stable release 20.11.5.
> >
> > Hi Luca,
> > this backport
> >
> https://git.dpdk.org/dpdk-stable/commit/?h=20.11&id=64452c878f225c147dfb7156e605f5b55da9f7c0
> > Causes symbol changes
> >
> https://launchpadlibrarian.net/593478119/buildlog_ubuntu-impish-amd64.dpdk_20.11.5~rc1-0ubuntu0.21.10.1~impishppa1_BUILDING.txt.gz
> >
> > There is an exception mentioned for 21.11, but would this also apply
> > for 20.11 or should we keep it stable there?
>
> Thanks for the heads-up, these looked like additions to the map file so
> I overlooked them. I'll revert this in the 20.11 tree, I don't think we
> should change symbols there.
>

Thanks, this breaks my test builds - will there be an RC2 with it or shall
I just revert it in-place for now?

-- 
> Kind regards,
> Luca Boccassi
>


-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

[-- Attachment #2: Type: text/html, Size: 2200 bytes --]

  reply	other threads:[~2022-03-28 12:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18 15:20 luca.boccassi
2022-03-23 13:33 ` Pei Zhang
2022-03-23 15:36   ` Luca Boccassi
2022-03-28  7:40 ` Christian Ehrhardt
2022-03-28 11:50   ` Luca Boccassi
2022-03-28 12:55     ` Christian Ehrhardt [this message]
2022-03-28 15:29       ` Luca Boccassi
2022-03-31 10:50         ` Christian Ehrhardt
2022-03-31 12:55           ` Luca Boccassi
2022-03-29 11:48 ` Jiang, YuX
2022-03-29 12:12   ` Luca Boccassi
2022-03-30 10:01   ` Jiang, YuX
2022-03-30  8:22 ` 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=CAATJJ0LyvfmWOB811Y3Kf6GGErAVoF3uAaX-qE0GYQS5JFM2cg@mail.gmail.com \
    --to=christian.ehrhardt@canonical.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).