From: Remy Horton <remy.horton@intel.com>
To: Jianfeng Tan <jianfeng.tan@intel.com>, dev@dpdk.org
Cc: ferruh.yigit@intel.com, david.marchand@6wind.com,
thomas.monjalon@6wind.com
Subject: Re: [dpdk-dev] [PATCH] doc: remove iomem and ioport handling in igb_uio
Date: Fri, 11 Nov 2016 10:12:22 +0800 [thread overview]
Message-ID: <330ff7fe-77e3-5ec9-7d2b-081ecb741877@intel.com> (raw)
In-Reply-To: <1474523045-2674-1-git-send-email-jianfeng.tan@intel.com>
On 22/09/2016 13:44, Jianfeng Tan wrote:
[..]
>
> Suggested-by: Yigit, Ferruh <ferruh.yigit@intel.com>
> Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
Acked-by: Remy Horton <remy.horton@intel.com>
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -57,3 +57,8 @@ Deprecation Notices
> * API will change for ``rte_port_source_params`` and ``rte_port_sink_params``
> structures. The member ``file_name`` data type will be changed from
> ``char *`` to ``const char *``. This change targets release 16.11.
As an aside I don't think changing a structure entry to const will
affect its binary layout, so this ought not be an ABI break..
next prev parent reply other threads:[~2016-11-11 2:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 2:16 [dpdk-dev] [RFC] igb_uio: deprecate iomem and ioport mapping Jianfeng Tan
2016-09-02 12:31 ` Ferruh Yigit
2016-09-02 12:59 ` Tan, Jianfeng
2016-09-09 9:06 ` David Marchand
2016-09-09 9:31 ` Tan, Jianfeng
2016-09-22 5:44 ` [dpdk-dev] [PATCH] doc: remove iomem and ioport handling in igb_uio Jianfeng Tan
2016-09-30 10:13 ` Ferruh Yigit
2016-11-11 2:12 ` Remy Horton [this message]
2016-11-13 8:55 ` Thomas Monjalon
2016-12-02 16:28 ` [dpdk-dev] [PATCH] igb_uio: deprecate iomem and ioport mapping Jianfeng Tan
2016-12-02 16:45 ` [dpdk-dev] [PATCH] igb_uio: stop device when closing /dev/uioX Jianfeng Tan
2017-03-30 20:22 ` Thomas Monjalon
2017-03-31 14:16 ` Ferruh Yigit
2016-12-02 23:47 ` [dpdk-dev] [RFC] igb_uio: deprecate iomem and ioport mapping Stephen Hemminger
2016-12-05 7:04 ` Tan, Jianfeng
2017-01-05 15:23 ` Ferruh Yigit
2017-01-06 1:52 ` Tan, Jianfeng
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=330ff7fe-77e3-5ec9-7d2b-081ecb741877@intel.com \
--to=remy.horton@intel.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jianfeng.tan@intel.com \
--cc=thomas.monjalon@6wind.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).