DPDK patches and discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: David Marchand <david.marchand@redhat.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
	ci@dpdk.org, dev <dev@dpdk.org>,  Ray Kinsella <mdr@ashroe.eu>
Subject: Re: [dpdk-dev] [dpdk-ci] [PATCH] version: 21.11-rc0
Date: Tue, 17 Aug 2021 08:04:30 -0400	[thread overview]
Message-ID: <CAOE1vsO_93nFY+8A2G_z-ZjXuoNAB3qFE0Liibwdxb56kSFQFg@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8z-bFDda2tFz9Hjp+KiDj7SgOXL3PS8L-A7bSKWchOzKw@mail.gmail.com>

Hi David,

ABI testing was disable / stopped on Friday in the Community CI lab.
Patches from before that for 21.11 would have still had the test run and
could have failures listed. I'm not sure if there is a way to "remove"
those failure marks from patchworks.  But, for all new patches since then,
ABI hasn't been run.

Cheers,
Lincoln

On Tue, Aug 17, 2021 at 2:34 AM David Marchand <david.marchand@redhat.com>
wrote:

> On Sun, Aug 8, 2021 at 9:27 PM Thomas Monjalon <thomas@monjalon.net>
> wrote:
> > diff --git a/doc/guides/rel_notes/release_21_11.rst
> b/doc/guides/rel_notes/release_21_11.rst
> > new file mode 100644
> > index 0000000000..d707a554ef
> > --- /dev/null
> > +++ b/doc/guides/rel_notes/release_21_11.rst
> > @@ -0,0 +1,136 @@
>
> [snip]
>
> > +Known Issues
> > +------------
> > +
> > +.. This section should contain new known issues in this release. Sample
> format:
> > +
> > +   * **Add title in present tense with full stop.**
> > +
> > +     Add a short 1-2 sentence description of the known issue
> > +     in the present tense. Add information on any known workarounds.
> > +
> > +   This section is a comment. Do not overwrite or remove it.
> > +   Also, make sure to start the actual text at the margin.
> > +   =======================================================
> > +
> > +
>
> The known issue "**Last mbuf segment not implicitly reset.**" added in
> 21.08 release notes still applies to 21.11.
> But this can be fixed later, patches are starting to accumulate and
> some CI failures are due to patches being applied to 21.08.
>
> The rest lgtm, so:
> Acked-by: David Marchand <david.marchand@redhat.com>
>
> Applied, thanks.
>
>
> On this last subject, this mail is a ping to CI labs owners.
> 21.11 release won't preserve ABI compat with previous releases, so
> please disable ABI checks until 22.02.
>
>
> --
> David Marchand
>
>

-- 
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>

  reply	other threads:[~2021-08-17 12:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-08 19:26 [dpdk-dev] " Thomas Monjalon
2021-08-12 14:36 ` Ferruh Yigit
2021-08-12 18:57   ` [dpdk-dev] [EXT] " Akhil Goyal
2021-08-17  6:34 ` [dpdk-dev] " David Marchand
2021-08-17 12:04   ` Lincoln Lavoie [this message]
2021-08-17 15:19     ` [dpdk-dev] [dpdk-ci] " David Marchand
2021-08-17 16:02       ` Ali Alnubani
2021-08-24  7:58     ` David Marchand
2021-08-24 12:19       ` Lincoln Lavoie

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=CAOE1vsO_93nFY+8A2G_z-ZjXuoNAB3qFE0Liibwdxb56kSFQFg@mail.gmail.com \
    --to=lylavoie@iol.unh.edu \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=mdr@ashroe.eu \
    --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).