From: Thomas Monjalon <thomas@monjalon.net>
To: Amit Prakash Shukla <amitprakashs@marvell.com>
Cc: Kevin Laatz <kevin.laatz@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
dev@dpdk.org, jerinj@marvell.com, conor.walsh@intel.com,
vattunuru@marvell.com, g.singh@nxp.com,
sachin.saxena@oss.nxp.com, hemant.agrawal@nxp.com,
cheng1.jiang@intel.com, ndabilpuram@marvell.com,
anoobj@marvell.com, mb@smartsharesystems.com,
fengchengwen <fengchengwen@huawei.com>
Subject: Re: [PATCH v2] test/dma: fix for buffer auto free
Date: Tue, 14 Nov 2023 15:58:59 +0100 [thread overview]
Message-ID: <9291839.DvuYhMxLoT@thomas> (raw)
In-Reply-To: <7980c3ec-7695-8a37-3f69-a91ded0b3165@huawei.com>
06/11/2023 02:08, fengchengwen:
> On 2023/11/4 2:30, Amit Prakash Shukla wrote:
> > Buffer auto free test failed for more than 1 dma device as the device
> > initialization for the test was been done only for the first dma
> > device. This changeset fixes the same and also fixes the freeing of
> > the uninitialised source buffer in error condition.
> >
> > Fixes: 877cb3e37426 ("dmadev: add buffer auto free offload")
> >
> > Signed-off-by: Amit Prakash Shukla <amitprakashs@marvell.com>
Acked-by: Chengwen Feng <fengchengwen@huawei.com>
Applied, thanks.
prev parent reply other threads:[~2023-11-14 14:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 10:18 [PATCH] " Amit Prakash Shukla
2023-11-01 14:08 ` Hemant Agrawal
2023-11-02 2:06 ` fengchengwen
2023-11-02 9:40 ` [EXT] " Amit Prakash Shukla
2023-11-03 18:30 ` [PATCH v2] " Amit Prakash Shukla
2023-11-06 1:08 ` fengchengwen
2023-11-14 14:58 ` 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=9291839.DvuYhMxLoT@thomas \
--to=thomas@monjalon.net \
--cc=amitprakashs@marvell.com \
--cc=anoobj@marvell.com \
--cc=bruce.richardson@intel.com \
--cc=cheng1.jiang@intel.com \
--cc=conor.walsh@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=g.singh@nxp.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=kevin.laatz@intel.com \
--cc=mb@smartsharesystems.com \
--cc=ndabilpuram@marvell.com \
--cc=sachin.saxena@oss.nxp.com \
--cc=vattunuru@marvell.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).