From: "Hunt, David" <david.hunt@intel.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ivshmem: fix for modified mempool struct
Date: Fri, 1 Jul 2016 17:37:07 +0100 [thread overview]
Message-ID: <a315bf13-ba80-2e33-ee93-b7be64cf6042@intel.com> (raw)
In-Reply-To: <1467390408-781-1-git-send-email-ferruh.yigit@intel.com>
On 1/7/2016 5:26 PM, Ferruh Yigit wrote:
> struct rte_mempool changed its "ring" field to "pool_data"
>
> "ring" field is accessed by ivshmem library, and updated to "pool_data"
>
> This patch fixes the compile error:
>
> == Build lib/librte_ivshmem
> CC rte_ivshmem.o
> .../lib/librte_ivshmem/rte_ivshmem.c:
> In function 'add_mempool_to_metadata':
> .../lib/librte_ivshmem/rte_ivshmem.c:584:32:
> error: 'const struct rte_mempool' has no member named 'ring'
> return add_ring_to_metadata(mp->ring, config);
> ^~
>
> Fixes: 449c49b93a6b ("mempool: support handler operations")
> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> ---
> lib/librte_ivshmem/rte_ivshmem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/librte_ivshmem/rte_ivshmem.c b/lib/librte_ivshmem/rte_ivshmem.c
> index 5c83920..c26edb6 100644
> --- a/lib/librte_ivshmem/rte_ivshmem.c
> +++ b/lib/librte_ivshmem/rte_ivshmem.c
> @@ -581,7 +581,7 @@ add_mempool_to_metadata(const struct rte_mempool *mp,
> }
>
> /* mempool consists of memzone and ring */
> - return add_ring_to_metadata(mp->ring, config);
> + return add_ring_to_metadata(mp->pool_data, config);
> }
>
> int
Acked-by: David Hunt <david.hunt@intel.com>
next prev parent reply other threads:[~2016-07-01 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 16:26 Ferruh Yigit
2016-07-01 16:37 ` Hunt, David [this message]
2016-07-01 17:32 ` Thomas Monjalon
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=a315bf13-ba80-2e33-ee93-b7be64cf6042@intel.com \
--to=david.hunt@intel.com \
--cc=dev@dpdk.org \
/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).