All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Huang, Wei" <wei.huang@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"Xu, Rosen" <rosen.xu@intel.com>,
	"Zhang, Tianfei" <tianfei.zhang@intel.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>
Subject: RE: [PATCH v1] doc/guides/nics: remove limitation of ipn3ke
Date: Fri, 24 Mar 2023 01:29:40 +0000	[thread overview]
Message-ID: <DM6PR11MB353088113199B0455F46C647EF849@DM6PR11MB3530.namprd11.prod.outlook.com> (raw)
In-Reply-To: <2814908.yaVYbkx8dN@thomas>



> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Thursday, March 23, 2023 16:53
> To: dev@dpdk.org; david.marchand@redhat.com; Huang, Wei
> <wei.huang@intel.com>
> Cc: stable@dpdk.org; Xu, Rosen <rosen.xu@intel.com>; Zhang, Tianfei
> <tianfei.zhang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Huang, Wei
> <wei.huang@intel.com>
> Subject: Re: [PATCH v1] doc/guides/nics: remove limitation of ipn3ke
> 
> 23/03/2023 02:00, Wei Huang:
> > Now ipn3ke is not evaluation in 19.05 .
> 
> What do you mean? It is not considered for evaluation since 19.05?
> Do you want to backport?
> 
No backport, this limitation is out of date, just to remove it.
> [...]
> > -19.05 limitation
> > -~~~~~~~~~~~~~~~~
> > -
> > -Ipn3ke code released in 19.05 is for evaluation only.
> >
> 
> 
> 
> 


  reply	other threads:[~2023-03-24  1:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23  1:00 [PATCH v1] doc/guides/nics: remove limitation of ipn3ke Wei Huang
2023-03-23  8:53 ` Thomas Monjalon
2023-03-24  1:29   ` Huang, Wei [this message]
2023-03-28 16:19     ` 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=DM6PR11MB353088113199B0455F46C647EF849@DM6PR11MB3530.namprd11.prod.outlook.com \
    --to=wei.huang@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=rosen.xu@intel.com \
    --cc=stable@dpdk.org \
    --cc=thomas@monjalon.net \
    --cc=tianfei.zhang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.