patches for DPDK stable branches
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Lance Richardson <lance.richardson@broadcom.com>
Cc: Declan Doherty <declan.doherty@intel.com>,
	 Pablo de Lara <pablo.de.lara.guarch@intel.com>,
	Chas Williams <chas3@att.com>,  "humin (Q)" <humin29@huawei.com>,
	dev <dev@dpdk.org>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] app/test: fix IPv6 header initialization
Date: Mon, 21 Jun 2021 14:49:08 +0200	[thread overview]
Message-ID: <CAJFAV8zB6wLtSKGWfyTuKWXcM24qFGX_DCvgjVe=_T+=rMkeyw@mail.gmail.com> (raw)
In-Reply-To: <CADyeNEAVti-J+8JVHw7ViZxwnt5TyS19cvCB08t7cj2sTK48=w@mail.gmail.com>

On Mon, Jun 21, 2021 at 2:41 PM Lance Richardson
<lance.richardson@broadcom.com> wrote:
>
> On Tue, May 11, 2021 at 10:42 AM Lance Richardson
> <lance.richardson@broadcom.com> wrote:
> >
> > On Tue, May 11, 2021 at 10:31 AM David Marchand
> > <david.marchand@redhat.com> wrote:
> > >
> > > On Fri, Mar 26, 2021 at 5:37 PM Lance Richardson
> > > <lance.richardson@broadcom.com> wrote:
> > > >
> > > > Fix two issues found when writing PMD unit tests for HW ptype and
> > > > L4 checksum offload:
> > >
> > > Would those unit tests be interesting to other pmd driver writers?
> > >
> > I think so, although some adjustments would be needed to account
> > for differences in hardware capabilities. The tests I've written so far
> > are still very much a work in progress, but I hope to have something
> > ready for RFC in the near future.
>
> What is the current status of this patch?

I wanted feedback from bonding guys, but I'll get it in v21.08 now.
Thanks for the heads up.


-- 
David Marchand


  reply	other threads:[~2021-06-21 12:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26 16:37 Lance Richardson
2021-05-11 14:31 ` David Marchand
2021-05-11 14:42   ` Lance Richardson
2021-06-21 12:40     ` Lance Richardson
2021-06-21 12:49       ` David Marchand [this message]
2021-07-05  8:22 ` David Marchand

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='CAJFAV8zB6wLtSKGWfyTuKWXcM24qFGX_DCvgjVe=_T+=rMkeyw@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=chas3@att.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=humin29@huawei.com \
    --cc=lance.richardson@broadcom.com \
    --cc=pablo.de.lara.guarch@intel.com \
    --cc=stable@dpdk.org \
    /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).