DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Lin, Xueqin" <xueqin.lin@intel.com>
To: "Chen, LingliX" <linglix.chen@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Chen, LingliX" <linglix.chen@intel.com>
Subject: RE: [PATCH V1] doc: add tested Intel platforms with Intel NICs
Date: Thu, 10 Mar 2022 15:15:51 +0000	[thread overview]
Message-ID: <SJ0PR11MB5599F61F3F6B1A2F320563FE940B9@SJ0PR11MB5599.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220310094619.495806-1-linglix.chen@intel.com>


> -----Original Message-----
> From: Lingli Chen <linglix.chen@intel.com>
> Sent: Thursday, March 10, 2022 5:46 PM
> To: dev@dpdk.org
> Cc: Chen, LingliX <linglix.chen@intel.com>
> Subject: [PATCH V1] doc: add tested Intel platforms with Intel NICs
> 
> Add tested Intel platforms with Intel NICs to v22.03 release note.
> 
> Signed-off-by: Lingli Chen <linglix.chen@intel.com>
Acked-by: Xueqin Lin <xueqin.lin@intel.com>

  reply	other threads:[~2022-03-10 15:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-10  9:46 Lingli Chen
2022-03-10 15:15 ` Lin, Xueqin [this message]
2022-03-13 12:10   ` Zhang, Qi Z
2022-03-10 17:23 ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2024-03-21 16:20 Yu Jiang
2024-03-25  2:48 ` Thomas Monjalon
2023-11-23  6:34 Lingli Chen
2023-11-24 14:15 ` David Marchand
2023-07-17  9:52 Lingli Chen
2023-07-20  4:53 ` Zhang, Qi Z
2023-03-22  5:51 Lingli Chen
2023-03-24  7:55 ` Peng, Yuan
2023-03-27 11:42   ` Zhang, Qi Z
2023-07-18 12:38 ` Peng, Yuan
2023-07-20  4:11   ` Zhang, Qi Z
2023-07-20  4:37     ` Thomas Monjalon
2023-07-20  4:51       ` Zhang, Qi Z
2022-11-17  4:36 Lingli Chen
2022-11-17  5:38 ` Peng, Yuan
2022-11-18  9:50   ` Zhang, Qi Z
2022-07-08  9:16 Lingli Chen
2022-07-11 21:42 ` Thomas Monjalon
2021-11-19 18:18 Yan Xia
2021-11-19 10:35 ` Lin, Xueqin
2021-11-24 15:33   ` 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=SJ0PR11MB5599F61F3F6B1A2F320563FE940B9@SJ0PR11MB5599.namprd11.prod.outlook.com \
    --to=xueqin.lin@intel.com \
    --cc=dev@dpdk.org \
    --cc=linglix.chen@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 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).