From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id EF3042BDF for ; Fri, 11 Nov 2016 03:12:26 +0100 (CET) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga104.jf.intel.com with ESMTP; 10 Nov 2016 18:12:25 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.31,620,1473145200"; d="scan'208";a="29966750" Received: from rhorton-mobl.ger.corp.intel.com (HELO [172.16.225.47]) ([172.16.225.47]) by fmsmga006.fm.intel.com with ESMTP; 10 Nov 2016 18:12:24 -0800 To: Jianfeng Tan , dev@dpdk.org References: <1472696197-37614-1-git-send-email-jianfeng.tan@intel.com> <1474523045-2674-1-git-send-email-jianfeng.tan@intel.com> Cc: ferruh.yigit@intel.com, david.marchand@6wind.com, thomas.monjalon@6wind.com From: Remy Horton Organization: Intel Shannon Limited Message-ID: <330ff7fe-77e3-5ec9-7d2b-081ecb741877@intel.com> Date: Fri, 11 Nov 2016 10:12:22 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.1.1 MIME-Version: 1.0 In-Reply-To: <1474523045-2674-1-git-send-email-jianfeng.tan@intel.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] doc: remove iomem and ioport handling in igb_uio X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Nov 2016 02:12:27 -0000 On 22/09/2016 13:44, Jianfeng Tan wrote: [..] > > Suggested-by: Yigit, Ferruh > Signed-off-by: Jianfeng Tan Acked-by: Remy Horton > +++ 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..