From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org, nikhil.agarwal@amd.com, nipun.gupta@amd.com,
david.marchand@redhat.com, thomas@monjalon.net,
anatoly.burakov@intel.com,
Shubham Rohila <shubham.rohila@amd.com>
Subject: Re: [PATCH] Add bus master enable/disable APIs for CDX devices
Date: Thu, 3 Oct 2024 23:48:43 +0100 [thread overview]
Message-ID: <72e19c0c-0fb1-4a83-9b06-833819285672@amd.com> (raw)
In-Reply-To: <20241003151640.0c0419a9@hermes.local>
On 10/3/2024 11:16 PM, Stephen Hemminger wrote:
> On Fri, 27 Oct 2023 17:22:11 +0100
> Ferruh Yigit <ferruh.yigit@amd.com> wrote:
>
>> From: Shubham Rohila <shubham.rohila@amd.com>
>>
>> Define rte_cdx_vfio_bm_enable and rte_cdx_vfio_bm_disable to
>> enable or disable bus master functionality for cdx devices.
>>
>> Signed-off-by: Shubham Rohila <shubham.rohila@amd.com>
>
> This version of the patch had lots test failures, could you clean
> up and resubmit.
>
v2 of the patch already merged.
Probably missed to update the status of this patch in the patchwork, I
will update it as 'superseded'
next prev parent reply other threads:[~2024-10-03 22:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 16:22 Ferruh Yigit
2023-10-27 16:24 ` Ferruh Yigit
2023-11-03 11:20 ` [PATCH v2 1/2] bus/cdx: add support for devices without MSI Shubham Rohila
2023-11-03 11:20 ` [PATCH v2 2/2] bus/cdx: add bus master enable/disable APIs Shubham Rohila
2023-11-07 14:25 ` Gupta, Nipun
2023-11-12 13:36 ` Thomas Monjalon
2023-11-06 17:04 ` [PATCH v2 1/2] bus/cdx: add support for devices without MSI Gupta, Nipun
2023-11-06 17:54 ` Agarwal, Nikhil
2023-11-07 14:25 ` Gupta, Nipun
2024-10-03 22:16 ` [PATCH] Add bus master enable/disable APIs for CDX devices Stephen Hemminger
2024-10-03 22:48 ` Ferruh Yigit [this message]
[not found] <20231026032009.3275263-1-shubham.rohila@amd.com>
2023-10-27 13:34 ` Gupta, Nipun
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=72e19c0c-0fb1-4a83-9b06-833819285672@amd.com \
--to=ferruh.yigit@amd.com \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=nikhil.agarwal@amd.com \
--cc=nipun.gupta@amd.com \
--cc=shubham.rohila@amd.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).