From: Akhil Goyal <gakhil@marvell.com>
To: Jerin Jacob <jerinjacobk@gmail.com>,
Srikanth Yalavarthi <syalavarthi@marvell.com>
Cc: Nicolas Chautru <nicolas.chautru@intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXT] Re: [PATCH 1/1] test/bbdev: use helper function to set IOVA addr
Date: Thu, 3 Nov 2022 08:01:37 +0000 [thread overview]
Message-ID: <CO6PR18MB448411D53400DA596683651ED8389@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <CALBAE1Pu4Zv0_sP-ZS=FPCuQ8ak=zYmRSZYBA+Yi=ctAud7APA@mail.gmail.com>
>
> On Thu, Nov 3, 2022 at 12:54 PM Srikanth Yalavarthi
> <syalavarthi@marvell.com> wrote:
> >
> > > On Tue, Nov 1, 2022 at 3:23 PM Srikanth Yalavarthi
> > > <syalavarthi@marvell.com> wrote:
> > > >
> > > > Use helper function rte_mbuf_iova_set to set IOVA address to fix
> > > > compilation failures.
> > > >
> > > > Below error was observed:
> > > >
> > > > dpdk/app/test-bbdev/test_bbdev_perf.c: In function ‘init_op_data_objs’:
> > > > dpdk/app/test-bbdev/test_bbdev_perf.c:1145:11: error:
> > > > ‘struct rte_mbuf’ has no member named ‘buf_iova’
> > > > 1145 | m_head->buf_iova = rte_malloc_virt2iova(data);
> > > > | ^~
> > > >
> > > > Fixes: 0acdb98667 ("test/bbdev: add FFT operations cases")
> > >
> > > Is this change came after rte_mbuf_iova_set() API introduction?
> > Yes, the change is need after rte_mbuf_iova_set API is added. Build failure is
> observed on x86 and ARM64.
>
> Then, Please change Fixes: as the changeset introduced the rte_mbuf_iova_set()
>
FFT patch was added after the new API was introduced. So Fixes should be the FFT patch only.
Applied to dpdk-next-crypto
prev parent reply other threads:[~2022-11-03 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 9:53 Srikanth Yalavarthi
2022-11-03 6:31 ` Jerin Jacob
2022-11-03 7:24 ` [EXT] " Srikanth Yalavarthi
2022-11-03 7:36 ` Jerin Jacob
2022-11-03 8:01 ` Akhil Goyal [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=CO6PR18MB448411D53400DA596683651ED8389@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinjacobk@gmail.com \
--cc=maxime.coquelin@redhat.com \
--cc=nicolas.chautru@intel.com \
--cc=syalavarthi@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).