DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Abdullah Sevincer <abdullah.sevincer@intel.com>
Cc: dev@dpdk.org, jerinj@marvell.com, mike.ximing.chen@intel.com,
	bruce.richardson@intel.com, chenbox@nvidia.com
Subject: Re: [PATCH v7 0/2] *** Disable PASID for DLB Device ***
Date: Mon, 06 Nov 2023 18:50:12 +0100	[thread overview]
Message-ID: <4619222.CvnuH1ECHv@thomas> (raw)
In-Reply-To: <20231106170521.3064038-1-abdullah.sevincer@intel.com>

06/11/2023 18:05, Abdullah Sevincer:
> This series implement an internal API to disable 
> PASID and calls the api to disable PASID in event/dlb2 device.
> 
> Abdullah Sevincer (2):
>   bus/pci: support PASID control
>   event/dlb2: fix disable PASID

Moved things in the right place/order and added PASID definition in Doxygen.

Applied, thanks.

PS: please keep all versions in the same mail thread.



      parent reply	other threads:[~2023-11-06 17:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 17:05 Abdullah Sevincer
2023-11-06 17:05 ` [PATCH v7 1/2] bus/pci: support PASID control Abdullah Sevincer
2023-11-06 18:30   ` David Marchand
2023-11-06 18:50     ` Sevincer, Abdullah
2023-11-10  8:03       ` David Marchand
2023-11-13 15:51         ` Sevincer, Abdullah
2023-11-13 17:36           ` Sevincer, Abdullah
2023-11-13 17:27   ` [PATCH v1] bus/pci: revise " Abdullah Sevincer
2023-11-14 13:59     ` Chenbo Xia
2023-11-14 17:39       ` Sevincer, Abdullah
2023-11-15  1:53         ` Chenbo Xia
2023-11-16 17:43           ` Chen, Mike Ximing
2023-11-17  6:48             ` Chenbo Xia
2023-11-14 17:36     ` [PATCH v2] " Abdullah Sevincer
2023-11-17  6:55       ` Chenbo Xia
2023-11-21 15:50         ` Thomas Monjalon
2023-11-06 17:05 ` [PATCH v7 2/2] event/dlb2: fix disable PASID Abdullah Sevincer
2023-11-06 17:50 ` 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=4619222.CvnuH1ECHv@thomas \
    --to=thomas@monjalon.net \
    --cc=abdullah.sevincer@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=chenbox@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=mike.ximing.chen@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).