patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Wei Huang <wei.huang@intel.com>,
	dev@dpdk.org, rosen.xu@intel.com, qi.z.zhang@intel.com
Cc: stable@dpdk.org, tianfei.zhang@intel.com
Subject: Re: [dpdk-stable] [PATCH v16 0/3] raw/ifpga: add extra APIs for Cyborg
Date: Wed, 17 Mar 2021 17:08:45 +0000	[thread overview]
Message-ID: <aa3852c3-ae32-954d-aeb6-012981862150@intel.com> (raw)
In-Reply-To: <1615967962-16062-1-git-send-email-wei.huang@intel.com>

On 3/17/2021 7:59 AM, Wei Huang wrote:
> Cyborg is part of OpenStack, it needs some extra APIs to manage
> devices with Intel FPGA. These patches add APIs to meet Cyborg
> requirement.
> 
> Main changes from v15:
> - remove example from the patch set
> 
> Wei Huang (3):
>    raw/ifpga: add fpga rsu APIs
>    raw/ifpga: add APIs to get fpga information
>    raw/ifpga: add miscellaneous APIs
> 

I guess this is sent by mistake, v16 already merged, updating patchwork accordingly.

  parent reply	other threads:[~2021-03-17 17:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  7:59 Wei Huang
2021-03-17  7:59 ` [dpdk-stable] [PATCH v16 1/3] raw/ifpga: add fpga rsu APIs Wei Huang
2021-03-17  7:59 ` [dpdk-stable] [PATCH v16 2/3] raw/ifpga: add APIs to get fpga information Wei Huang
2021-03-17  7:59 ` [dpdk-stable] [PATCH v16 3/3] raw/ifpga: add miscellaneous APIs Wei Huang
2021-03-17 17:08 ` Ferruh Yigit [this message]
2021-03-18  1:02   ` [dpdk-stable] [PATCH v16 0/3] raw/ifpga: add extra APIs for Cyborg Huang, Wei
  -- strict thread matches above, loose matches on Subject: below --
2021-03-03  2:34 Wei Huang
2021-03-05  8:54 ` Zhang, Qi Z

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=aa3852c3-ae32-954d-aeb6-012981862150@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.com \
    --cc=rosen.xu@intel.com \
    --cc=stable@dpdk.org \
    --cc=tianfei.zhang@intel.com \
    --cc=wei.huang@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).