DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Beilei Xing <beilei.xing@intel.com>
Cc: jingjing.wu@intel.com, dev@dpdk.org
Subject: Re: [PATCH v2] doc: update release notes for Intel IPU
Date: Thu, 27 Jul 2023 22:40:13 +0200	[thread overview]
Message-ID: <2149622.irdbgypaU6@thomas> (raw)
In-Reply-To: <20230721145839.1018100-1-beilei.xing@intel.com>

21/07/2023 16:58, beilei.xing@intel.com:
> From: Beilei Xing <beilei.xing@intel.com>
> 
> Update release notes for Intel IPU new features:
>  - Support VF whose device id is 0x145c.
>  - Support hairpin queue.
> 
> Fixes: 32bcd47e16fe ("net/idpf: support VF")
> Fixes: 1ec8064832db ("net/cpfl: add haipin queue group during vport init")
> 
> Signed-off-by: Beilei Xing <beilei.xing@intel.com>
> Acked-by: Jingjing Wu <jingjing.wu@intel.com>

Applied




      reply	other threads:[~2023-07-27 20:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28 15:38 [PATCH] " beilei.xing
2023-07-03  2:50 ` Wu, Jingjing
2023-07-21 14:58 ` [PATCH v2] " beilei.xing
2023-07-27 20:40   ` Thomas Monjalon [this message]

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=2149622.irdbgypaU6@thomas \
    --to=thomas@monjalon.net \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@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).