DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Abhishek Maheshwari <abhishek.maheshwari@intel.com>,
	xiao.w.wang@intel.com
Cc: dev@dpdk.org, stable@dpdk.org, chenbo.xia@intel.com,
	purna.chandra.mandal@intel.com
Subject: Re: [PATCH v4] vdpa/ifc: Match default subsystem IDs for modern virtio-blk devices
Date: Fri, 3 Feb 2023 15:57:56 +0100	[thread overview]
Message-ID: <aa7fbad4-cc91-adea-79fc-75f26889c636@redhat.com> (raw)
In-Reply-To: <20221215034818.2145612-1-abhishek.maheshwari@intel.com>



On 12/15/22 04:48, Abhishek Maheshwari wrote:
> Amending the match table for vdpa/ifcvf driver to work with virtio-blk
> devices that have default subsystem IDs.
> 
> Cc: stable@dpdk.org
> 
> Signed-off-by: Abhishek Maheshwari <abhishek.maheshwari@intel.com>
> 
> ---
> v3:
> * Removing match with ANY_IDs
> * Adding support for only default subsystem IDs
> 
> v2:
> * commit message update
> ---
>   drivers/vdpa/ifc/base/ifcvf.h | 1 +
>   drivers/vdpa/ifc/ifcvf_vdpa.c | 7 +++++++
>   2 files changed, 8 insertions(+)
> 

Applied to dpdk-next-virtio/main.

Thanks,
Maxime


      parent reply	other threads:[~2023-02-03 14:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 12:50 [PATCH] vdpa/ifc: Match ANY subsystem IDs for modern virtio devices Abhishek Maheshwari
2022-12-06 12:55 ` [PATCH v2] " Abhishek Maheshwari
2022-12-08 13:08   ` Wang, Xiao W
2022-12-09  2:37     ` Pei, Andy
2022-12-15  3:42   ` [PATCH v3] vdpa/ifc: Match default subsystem IDs for modern virtio-blk devices Abhishek Maheshwari
2022-12-15  3:48     ` [PATCH v4] " Abhishek Maheshwari
2022-12-16  1:58       ` Pei, Andy
2023-01-19 14:09       ` Maxime Coquelin
2023-02-03 14:57       ` Maxime Coquelin [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=aa7fbad4-cc91-adea-79fc-75f26889c636@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=abhishek.maheshwari@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=dev@dpdk.org \
    --cc=purna.chandra.mandal@intel.com \
    --cc=stable@dpdk.org \
    --cc=xiao.w.wang@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).