DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Sebastian, Selwin" <Selwin.Sebastian@amd.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	David Marchand <david.marchand@redhat.com>,
	 "Varghese, Vipin" <Vipin.Varghese@amd.com>,
	"Tummala, Sivaprasad" <Sivaprasad.Tummala@amd.com>
Subject: RE: [dpdk-dev] [RFC PATCH v2] raw/ptdma: introduce ptdma driver
Date: Thu, 16 Jun 2022 14:27:46 +0000	[thread overview]
Message-ID: <DM4PR12MB5055BA52FCE7D3D3FE0850628DAC9@DM4PR12MB5055.namprd12.prod.outlook.com> (raw)
In-Reply-To: <2041723.VLH7GnMWUR@thomas>

[AMD Official Use Only - General]

We were having issues with iommu. Now we will try to push the patch without iommu enabled. Will split patch into smaller ones and submit soon.

Thanks,
Selwin


-----Original Message-----
From: Thomas Monjalon <thomas@monjalon.net>
Sent: Wednesday, June 15, 2022 8:06 PM
To: Sebastian, Selwin <Selwin.Sebastian@amd.com>
Cc: dev@dpdk.org; David Marchand <david.marchand@redhat.com>; Varghese, Vipin <Vipin.Varghese@amd.com>; Tummala, Sivaprasad <Sivaprasad.Tummala@amd.com>
Subject: Re: [dpdk-dev] [RFC PATCH v2] raw/ptdma: introduce ptdma driver

[CAUTION: External Email]

28/10/2021 16:54, Sebastian, Selwin:
> I am working on making ptdma driver as a dmadev.  Will submit new patch for review.

Any update?




  reply	other threads:[~2022-06-16 14:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-06 16:55 Selwin Sebastian
2021-09-06 17:17 ` David Marchand
2021-10-27 14:59   ` Thomas Monjalon
2021-10-28 14:54     ` Sebastian, Selwin
2022-06-15 14:35       ` Thomas Monjalon
2022-06-16 14:27         ` Sebastian, Selwin [this message]
2023-06-28  9:08           ` Ferruh Yigit
  -- strict thread matches above, loose matches on Subject: below --
2021-09-06 15:59 Selwin Sebastian
2021-09-06 14:34 Selwin Sebastian

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=DM4PR12MB5055BA52FCE7D3D3FE0850628DAC9@DM4PR12MB5055.namprd12.prod.outlook.com \
    --to=selwin.sebastian@amd.com \
    --cc=Sivaprasad.Tummala@amd.com \
    --cc=Vipin.Varghese@amd.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.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).