DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Shubham Rohila <shubham.rohila@amd.com>
Cc: nikhil.agarwal@amd.com, david.marchand@redhat.com, dev@dpdk.org,
	ferruh.yigit@amd.com, anatoly.burakov@intel.com, "Gupta,
	Nipun" <nipun.gupta@amd.com>
Subject: Re: [PATCH v2 2/2] bus/cdx: add bus master enable/disable APIs
Date: Sun, 12 Nov 2023 14:36:56 +0100	[thread overview]
Message-ID: <2161608.irdbgypaU6@thomas> (raw)
In-Reply-To: <a44e58b0-4878-4825-9c91-6b3c02ed7594@amd.com>

07/11/2023 15:25, Gupta, Nipun:
> 
> On 11/3/2023 4:50 PM, Shubham Rohila wrote:
> > 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>
> > ---
> >   v2
> >   - Fix indentations and alphabetical orderings.
> >   - Wrap checks in parenthesis for readability
> >   - Assign argsz before using in rte_cdx_vfio_bm_disable
> >   - Remove unecessary variable initialisation
> 
> Acked-by: Nipun Gupta <nipun.gupta@amd.com>

Applied, thanks.



  reply	other threads:[~2023-11-12 13:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27 16:22 [PATCH] Add bus master enable/disable APIs for CDX devices 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 [this message]
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

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=2161608.irdbgypaU6@thomas \
    --to=thomas@monjalon.net \
    --cc=anatoly.burakov@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.com \
    --cc=nikhil.agarwal@amd.com \
    --cc=nipun.gupta@amd.com \
    --cc=shubham.rohila@amd.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).