From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Olivier Matz <olivier.matz@6wind.com>, rkerur@gmail.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v5] mbuf: introduce common functions to get dma address
Date: Fri, 04 Mar 2016 15:52:03 +0100 [thread overview]
Message-ID: <2238090.dQRaXJiXYV@xps13> (raw)
In-Reply-To: <1457082580-19289-1-git-send-email-olivier.matz@6wind.com>
2016-03-04 10:09, Olivier Matz:
> From: Ravi Kerur <rkerur@gmail.com>
>
> Macros RTE_MBUF_DATA_DMA_ADDR and RTE_MBUF_DATA_DMA_ADDR_DEFAULT
> are defined in each PMD driver file. Convert macros to inline
> functions and move them to common lib/librte_mbuf/rte_mbuf.h file.
> PMD drivers include rte_mbuf.h file directly/indirectly hence no
> additioanl header file inclusion is necessary.
>
> Signed-off-by: Ravi Kerur <rkerur@gmail.com>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
Applied, thanks
prev parent reply other threads:[~2016-03-04 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 11:58 [dpdk-dev] [PATCH v4] Move rte_mbuf macros to common header file Ravi Kerur
2016-03-04 9:09 ` [dpdk-dev] [PATCH v5] mbuf: introduce common functions to get dma address Olivier Matz
2016-03-04 14:52 ` 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=2238090.dQRaXJiXYV@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=rkerur@gmail.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).